Differences between revisions 3 and 4
Revision 3 as of 2017-12-06 20:31:23
Size: 1672
Editor: AugieFackler
Comment:
Revision 4 as of 2017-12-06 21:24:32
Size: 1976
Editor: KevinBullock
Comment: add -S/--subrepos deprecation
Deletions are marked like this. Additions are marked like this.
Line 28: Line 28:
== Make -S/--subrepos flags unnecessary ==

It has always been the intention to make commands like `hg status`, `hg add`, `hg remove`, etc. handle subrepos transparently. The way to go about that is [[https://www.mercurial-scm.org/pipermail/mercurial-devel/2011-October/034816.html|outlined here]].

Note:

This page is primarily intended for developers of Mercurial.

Good Ideas for Enhancements

Ideas that the community has discussed and largely approved of, but no one has yet implemented. This is somewhat distinct from Plan pages, although the two lists may overlap.

Projects listed here may be a good starting point for new contributors wanting to take on a more significant contribution than fixing "easy" bugs, without having to take on an up-front design discussion.

1. Expect Revset

expect(<set>, <int>) revset: fails if <set> isn’t exactly <int> elements

expect(<set>, <min>, <max>) revset: fails if <set> isn’t exactly between <min> and <max> inclusive

one(<set>) alias for expect(<set>, 1)

This then allows an alias for hg next to be update -r one(children(.)) with sane failure behavior, and also makes some other scripting tasks a little less difficult.

2. hg shellprompt

hg shellprompt bash "{branch} {node|shortest}": emits string for eval in bash to efficiently produce the specified template. Opens the door to first-part native prompt helpers that don’t have to start a Python. Prior art in docker’s command line tools?

3. Make `hg grep` do what people expect

See GrepPlan for details. Not a small project, but would be greatly appreciated by many users.

4. Make -S/--subrepos flags unnecessary

It has always been the intention to make commands like hg status, hg add, hg remove, etc. handle subrepos transparently. The way to go about that is outlined here.

5. See Also


CategoryDeveloper CategoryNewFeatures

WeShouldDoThat (last edited 2020-09-25 04:26:54 by MattHarbison)