[PATCH 1 of 1] outgoing: respect ":pushurl" paths

Hollis Blanchard hollis_blanchard at mentor.com
Fri Nov 3 15:01:09 EDT 2017

On 11/03/2017 11:25 AM, Hollis Blanchard wrote:
> # HG changeset patch
> # User Hollis Blanchard <hollis_blanchard at mentor.com>
> # Date 1509731952 25200
> #      Fri Nov 03 10:59:12 2017 -0700
> # Branch stable
> # Node ID 666d3aaffadc4e92acfe3e4098ae8f2fa4086b7d
> # Parent  f445b10dc7fb3495d24d1c22b0996148864c77f7
> outgoing: respect ":pushurl" paths
> Make 'hg outgoing' respect "paths.default:pushurl" in addition to
> "paths.default-push".
Here's some context I didn't think belonged in the commit message:

'hg outgoing' has always meant "what will happen if I run 'hg push'?" 
and it's
still documented that way:

     Show changesets not found in the specified destination repository 
or the
     default push location. These are the changesets that would be 
pushed if a
     push was requested.

If the user uses the now-deprecated "paths.default-push" path, it 
continues to
work that way. However, as described at
https://bz.mercurial-scm.org/show_bug.cgi?id=5365, it doesn't behave the 
with "paths.default:pushurl".

Why does it matter? Similar to the bugzilla reporter, I have a read-only 
of a non-Mercurial repository:

upstream -> imported mirror -> user clone

Users push directly to upstream, and that content is then imported into the
mirror. However, those repositories are not the same; it's possible that the
mirroring has either broken completely, or an import process is running 
and not
yet complete. In those cases, 'hg outgoing' will list changesets that have
already been pushed.

Mozilla's desired behavior described in bug 5365 can be accomplished through
other means (e.g. 'hg outgoing default'), preserving the consistency and
meaning of 'hg outgoing'.

Hollis Blanchard <hollis_blanchard at mentor.com>
Mentor Graphics Emulation Division

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mercurial-scm.org/pipermail/mercurial-devel/attachments/20171103/7e60a169/attachment.html>

More information about the Mercurial-devel mailing list