Martin von Zweigbergk 18d73bc673 docs: don't say "both inclusive" about x:y and x..y revset endpoint ... We currently say that `x..y` is "Ancestors of `y` that are not also ancestors of `x`, both inclusive.". However, it's easy to think that "both inclusive" means that both `x` and `y` are included in the set, which is not the case. What we mean is more like "{Ancestors of `y`, including `y` itself} that are not also {ancestors of `x`, including `x` itself}.". Given that we already define ancestors and descendants as being inclusive on the lines above, and we also give the equivalent expressions using the `x:` and `:y` operators, it's probably best to just skip the "both inclusive" parts.		2023-05-05 22:26:27 -07:00
..
design	docs/design: propose submodule storage approach	2023-04-24 14:29:47 -07:00
technical
branches.md
code-of-conduct.md
config.md	Fix small typo	2023-04-18 18:03:05 +09:00
config.toml
conflicts.md
contributing.md
git-comparison.md
git-compatibility.md
github.md
glossary.md	docs: add a glossary	2023-04-17 16:48:23 -07:00
operation-log.md
related-work.md
revsets.md	docs: don't say "both inclusive" about x:y and x..y revset endpoint	2023-05-05 22:26:27 -07:00
templates.md
tutorial.md
working-copy.md