[Bug 5000] New: `hg push default`uses default-push path
mercurial-bugs at selenic.com
mercurial-bugs at selenic.com
Mon Dec 14 16:07:00 UTC 2015
https://bz.mercurial-scm.org/show_bug.cgi?id=5000
Bug ID: 5000
Summary: `hg push default`uses default-push path
Product: Mercurial
Version: 3.6.2
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: bug
Priority: wish
Component: Mercurial
Assignee: bugzilla at selenic.com
Reporter: computersarehrd at gmail.com
CC: mercurial-devel at selenic.com
Issue:
When `default-push` is specified in .hgrc, the command `hg push default` will
use the `default-push` path instead of `default` as specified by the command.
This is a regression from 3.5.2 which correctly pushes to the `default` path.
Steps to reproduce:
$ hg --version
Mercurial Distributed SCM (version 3.6.2)
Enabled extensions:
$ hg init push-bug
$ hg clone push-bug push-bug-fork
updating to branch default
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
$ hg clone push-bug push-bug-wc
updating to branch default
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
$ cd push-bug-wc
$ hg paths
default = /home/peter/push-bug
default-push = /home/peter/push-bug-fork
$ echo a > a
$ hg commit -A -m 'a'
$ hg out default
comparing with /home/peter/push-bug
searching for changes
0:491573317e72:default (draft) [tip] - peter
a
$ hg push default
pushing to /home/peter/push-bug-fork
searching for changes
1 changesets found
...
Note how `outgoing` compares with the default path, but `push` pushes to the
default-push path
Versions:
This has been observed in 3.6, 3.6.1, and 3.6.2 on Linux, OS X, and FreeBSD.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the Mercurial-devel
mailing list