[Bug 5514] New: commands.rebase.requiredest and commands.update.requiredest break `hg pull --rebase`

mercurial-bugs at mercurial-scm.org mercurial-bugs at mercurial-scm.org
Fri Mar 24 19:26:46 UTC 2017


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

            Bug ID: 5514
           Summary: commands.rebase.requiredest and
                    commands.update.requiredest break `hg pull --rebase`
           Product: Mercurial
           Version: default branch
          Hardware: PC
                OS: Linux
            Status: UNCONFIRMED
          Severity: bug
          Priority: wish
         Component: Mercurial
          Assignee: bugzilla at mercurial-scm.org
          Reporter: hg at pewpew.net
                CC: mercurial-devel at mercurial-scm.org, rm at fb.com

Created attachment 1953
  --> https://bz.mercurial-scm.org/attachment.cgi?id=1953&action=edit
Test that should not pass, demonstrating issue.

Using hg version: 4.1.1+716-772878ac930e

commands.rebase.requiredest and commands.update.requiredest break `hg pull
--rebase`:

`hg pull --rebase` does not allow one to specify a destination.  Requiring that
we specify a destination for `hg pull --rebase` doesn't really work then ;)

Both options are relevant, since if there's nothing to rebase, `hg pull
--rebase` falls back to doing an update.  

Example showing the problems are attached, but it's what you might expect: it
asks for a destination. If rebase.requiredest is on, it *always* mentions `hg
rebase -d dest`, if rebase.requiredest is off but update.requiredest is on, and
it's a rebase-less pull (so it does an update), it mentions `hg update`.

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


More information about the Mercurial-devel mailing list