[PATCH 3 of 3] transaction-summary: display the range of new revisions upon pull/unbundle

Augie Fackler raf at durin42.com
Wed Oct 11 15:46:30 EDT 2017


On Wed, Oct 04, 2017 at 06:52:45PM +0200, Denis Laxalde wrote:
> # HG changeset patch
> # User Denis Laxalde <denis.laxalde at logilab.fr>
> # Date 1507135871 -7200
> #      Wed Oct 04 18:51:11 2017 +0200
> # Node ID ae007b70b03657bbb92f4b73e6e0c807669dae10
> # Parent  211188885b0000b034eb168806d485b3b28c3112
> # Available At http://hg.logilab.org/users/dlaxalde/hg
> #              hg pull http://hg.logilab.org/users/dlaxalde/hg -r ae007b70b036
> # EXP-Topic pull-info-transaction
> transaction-summary: display the range of new revisions upon pull/unbundle

I've taken the first two patches, but this one at least merits (BC)
flagging I think. I like the feature though, so please mail a v2 of
this patch for further discussion.

>
> Upon pull or unbundle, we display a message with the range of new revisions
> fetched. This revision range could readily be used after a pull to look out
> what's new with 'hg log'. The algorithm takes care of filtering "obsolete"
> revisions that might be present in transaction's "changes" but should not be
> displayed to the end user.

Does this series open the door to informing the user how many changes
moved from draft to public?


More information about the Mercurial-devel mailing list