[Bug 6433] New: duplicated output for `hg next` when ambiguous changesets

mercurial-bugs at mercurial-scm.org mercurial-bugs at mercurial-scm.org
Sun Nov 15 16:15:09 UTC 2020


https://bz.mercurial-scm.org/show_bug.cgi?id=6433

            Bug ID: 6433
           Summary: duplicated output for `hg next` when ambiguous
                    changesets
           Product: Mercurial
           Version: default branch
          Hardware: PC
                OS: Linux
            Status: UNCONFIRMED
          Severity: feature
          Priority: wish
         Component: evolution
          Assignee: bugzilla at mercurial-scm.org
          Reporter: rom1dep at gmail.com
                CC: mercurial-devel at mercurial-scm.org,
                    pierre-yves.david at ens-lyon.org
    Python Version: ---

Here is the effect of running hg next on evolve's d75cea88bc4b (hg's id being
de1f4c431619)

mutable-history(hg)[ stable ]➤ hg next
ambiguous next changeset, choose one to update:
1: [4c1eb455259f] branching: merge stable into default
2: [a168d186ed79] tests: add more merge+successors cases for stack
3: [44d643d38b21] docs: refactor docs/conf.py a bit
4: [0e397aeee55b] tests: update comment in test-check-pyflakes.t
5: [36e5360fa0a9] tests: add a new test-check-tag.t to test releases
q: quit the prompt
enter the index of the revision you want to select: q
ambiguous next changeset:
[6351] branching: merge stable into default
[6352] tests: add more merge+successors cases for stack
[6359] docs: refactor docs/conf.py a bit
[6371] tests: update comment in test-check-pyflakes.t
[6383] tests: add a new test-check-tag.t to test releases
explicitly update to one of them

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the Mercurial-devel mailing list