[PATCH 1 of 3 V3] cmdutil: add support for evolution "troubles" display in changeset_printer

# HG changeset patch # User Denis Laxalde <denis.laxa...@logilab.fr> # Date 1476094018 -7200 # Mon Oct 10 12:06:58 2016 +0200 # Node ID 3c3bce29816f8cd0b176f450ab2e1ad854d5551b # Parent d06c049695e6ad3219e7479c65ce98a2f123e878 # EXP-Topic evolve-ui cmdutil: add support for evo

[PATCH 2 of 3 V3] templates: display evolution "troubles" in command line style

# HG changeset patch # User Denis Laxalde <denis.laxa...@logilab.fr> # Date 1478597306 -3600 # Tue Nov 08 10:28:26 2016 +0100 # Node ID 39f09e0ffdc5591cf87f200c9a99b97ca4e9abcc # Parent 3c3bce29816f8cd0b176f450ab2e1ad854d5551b # EXP-Topic evolve-ui templates: display evolution &qu

[PATCH 3 of 3 V3] summary: add evolution "troubles" information to parents header lines

# HG changeset patch # User Denis Laxalde <denis.laxa...@logilab.fr> # Date 1475935828 -7200 # Sat Oct 08 16:10:28 2016 +0200 # Node ID c240e26577a58e7c42cabce8f66a0c236a1167dd # Parent 39f09e0ffdc5591cf87f200c9a99b97ca4e9abcc # EXP-Topic evolve-ui summary: add evolution &qu

Re: [PATCH 1 of 3 V2] cmdutil: add support for evolution "troubles" display in changeset_printer

Pierre-Yves David a écrit : How about "stability"? If it feels strange to only have it displayed when there are "troubles", we may also insert it in the debug section as `stability: stable`. I do not think it is suitable, stability does not really fit for "divergent" or "bumped" and too linked

[PATCH 1 of 3 V2] cmdutil: add support for evolution "troubles" display in changeset_printer

# HG changeset patch # User Denis Laxalde <denis.laxa...@logilab.fr> # Date 1476094018 -7200 # Mon Oct 10 12:06:58 2016 +0200 # Node ID 8be06285117259ddd122201b1e0428711c0e2a6b # Parent d06c049695e6ad3219e7479c65ce98a2f123e878 # EXP-Topic evolve-ui cmdutil: add support for evo

[PATCH 3 of 3 V2] summary: add evolution "troubles" information to parents header lines

# HG changeset patch # User Denis Laxalde <denis.laxa...@logilab.fr> # Date 1475935828 -7200 # Sat Oct 08 16:10:28 2016 +0200 # Node ID 35c0f05d694cb9541d60bad9a940cb93a39d615d # Parent b5d3d230bbc64d44968a9912e8e72aac8236522a # EXP-Topic evolve-ui summary: add evolution &qu

[PATCH 2 of 3 V2] templates: display evolution "troubles" in command line style

# HG changeset patch # User Denis Laxalde <denis.laxa...@logilab.fr> # Date 1478597306 -3600 # Tue Nov 08 10:28:26 2016 +0100 # Node ID b5d3d230bbc64d44968a9912e8e72aac8236522a # Parent 8be06285117259ddd122201b1e0428711c0e2a6b # EXP-Topic evolve-ui templates: display evolution &qu

Re: [PATCH 3 of 3] summary: add evolution "troubles" information to parents header lines

Yuya Nishihara a écrit : On Mon, 10 Oct 2016 14:33:19 +0200, Denis Laxalde wrote: # HG changeset patch # User Denis Laxalde <denis.laxa...@logilab.fr> # Date 1475935828 -7200 # Sat Oct 08 16:10:28 2016 +0200 # Node ID 1ec84349bfa3db4e753f9084837c7ea2f0c3a4b9 #

[PATCH RESEND] revert: do not reverse hunks in interactive when REV is not parent (issue5096)

# HG changeset patch # User Denis Laxalde <denis.laxa...@logilab.fr> # Date 1475237490 -7200 # Fri Sep 30 14:11:30 2016 +0200 # Node ID 4f7b7750403ce48e78d0f361236f65ac03584c3c # Parent d06c049695e6ad3219e7479c65ce98a2f123e878 revert: do not reverse hunks in interactive wh

Re: [PATCH 2 of 2] commands: introduce `hg display`

eplacement to the aforementioned alias I guess. Given this and the conflict with `hg diff`, could we reconsider the command name? -- Denis Laxalde Logilab http://www.logilab.fr ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www

Re: [PATCH 1 of 2] commands: add "di" alias for "diff"

Jun Wu a écrit : Therefore I'm very sensitive about this. I think we should always make sure "d" = "diff" (although the complaint was only about "di"). I'm also quite used to `hg d`, for what it's worth. ___ Mercurial-devel mailing list

Re: history at diff blocks level

alculation. It seems to me that high level diff function like "mdiff.unidiff" could take an extra parameter "difffunc" which defaults to "allblocks". Then we can have a "filteredallblocks" passed to "unidiff". Thanks for these hints, I'll try to dig this way as soon as I get back to this topic. -- Denis Laxalde Logilab http://www.logilab.fr ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel

Re: [PATCH] color: replace "purple_background" by "magenta_background"

Pierre-Yves David a écrit : On 10/11/2016 11:39 AM, Denis Laxalde wrote: # HG changeset patch # User Denis Laxalde <denis.laxa...@logilab.fr> # Date 1476176128 -7200 # Tue Oct 11 10:55:28 2016 +0200 # Node ID 1cf20c1c54cb8172816604de5e1d98d3cd62d711 #

[PATCH] color: replace "purple_background" by "magenta_background"

# HG changeset patch # User Denis Laxalde <denis.laxa...@logilab.fr> # Date 1476176128 -7200 # Tue Oct 11 10:55:28 2016 +0200 # Node ID 1cf20c1c54cb8172816604de5e1d98d3cd62d711 # Parent b85fa6bf298be07804a74d8fdec0d19fdbc6d740 # EXP-Topic color-purple-crash color: replace "purple

Re: news from the topic experiment

`hg pull` to explicitly pull some topic(s). Here, this diverges from `hg pull` behavior with respect to named branches (all branches are pulled by default). But this might be an occasion to "fix" things? -- Denis Laxalde Logilab http://www.logilab.fr

history at diff blocks level

hich "tool" I may use to achieve this (I thought about using the "filematcher" built along with "revs" in commands.log(), but not really sure it's a good idea). Maybe I just need a data structure that does not exist yet? I'd appreciate any pointer to move forward. (I'll be at

<    1   2   3   4   5   6