Re: [PATCH] update: remove dead (?) code about non-linear updates

On Tue, Feb 7, 2017 at 1:29 PM, Martin von Zweigbergk wrote: > # HG changeset patch > # User Martin von Zweigbergk > # Date 1486501890 28800 > # Tue Feb 07 13:11:30 2017 -0800 > # Node ID 0659349ff46b2d449ceb02fe01b63053d8a43a13 > # Parent

Re: [PATCH] zeroconf: fail nicely on IPv6 only system

This does not work if the hardcoded 127.0.0.1 is not known to the system: sudo ip addr del 127.0.0.1/8 dev lo # on Linux That could happen if the system is IPv6-only, or only has other addresses in the 127./8 subnet like 127.0.0.2, or does not have a "lo" device. I think the pathological

[PATCH 2 of 4 RFC] chgcache: implement simple IPC mechanism

# HG changeset patch # User Jun Wu # Date 1486601798 28800 # Wed Feb 08 16:56:38 2017 -0800 # Node ID 8410c4a6703bed4b459cf8d62bd32fdcb1e7 # Parent 138f7ba58a70de9610713b8bd55d1ba0ac468fa6 # Available At https://bitbucket.org/quark-zju/hg-draft # hg pull

[PATCH 1 of 4 RFC] chgcache: new experimental extension

# HG changeset patch # User Jun Wu # Date 1486601732 28800 # Wed Feb 08 16:55:32 2017 -0800 # Node ID 138f7ba58a70de9610713b8bd55d1ba0ac468fa6 # Parent a68510b69f413545722c086eaeb840dd5e8305b4 # Available At https://bitbucket.org/quark-zju/hg-draft # hg pull

[PATCH 4 of 4 RFC] chgcache: add the background preloading thread

# HG changeset patch # User Jun Wu # Date 1486604289 28800 # Wed Feb 08 17:38:09 2017 -0800 # Node ID 79adf3722f1b0f602e9461f13fa940a25dbfce56 # Parent 88c498ad9318df115d8408412a38edbac7d92a6a # Available At https://bitbucket.org/quark-zju/hg-draft # hg pull

[PATCH 3 of 4 RFC] chgcache: report repo paths from worker to master

# HG changeset patch # User Jun Wu # Date 1486603691 28800 # Wed Feb 08 17:28:11 2017 -0800 # Node ID 88c498ad9318df115d8408412a38edbac7d92a6a # Parent 8410c4a6703bed4b459cf8d62bd32fdcb1e7 # Available At https://bitbucket.org/quark-zju/hg-draft # hg pull

[PATCH 2 of 2 V2] commandserver: handle backlog before exiting

# HG changeset patch # User Jun Wu # Date 1486593930 28800 # Wed Feb 08 14:45:30 2017 -0800 # Node ID cb56fce57eceef2cf4cd9893d387b9fe2b3cecd6 # Parent 5fc577761fb78168fcbd7ec93d911a1b7b4989c9 # Available At https://bitbucket.org/quark-zju/hg-draft # hg pull

[PATCH 1 of 2 V2] commandserver: prevent unlink socket twice

# HG changeset patch # User Jun Wu # Date 1486593458 28800 # Wed Feb 08 14:37:38 2017 -0800 # Node ID 5fc577761fb78168fcbd7ec93d911a1b7b4989c9 # Parent a68510b69f413545722c086eaeb840dd5e8305b4 # Available At https://bitbucket.org/quark-zju/hg-draft # hg pull

Re: [PATCH 1 of 3 pager-in-core-prep] pager: add a test of --pager=no functionality

On Tue, Feb 7, 2017 at 2:23 PM, Augie Fackler wrote: > These three patches are the prep work for a long series that moves > pager to core and makes it on by default. > These 3 look good. Thanks! ___ Mercurial-devel mailing list

Re: [PATCH] pager: exit cleanly on SIGPIPE (BC)

On Wed, Feb 08, 2017 at 07:47:39AM -0800, Simon Farnsworth wrote: > # HG changeset patch > # User Simon Farnsworth > # Date 1486568650 28800 > # Wed Feb 08 07:44:10 2017 -0800 > # Node ID d50cda2a403786836d1f0d5c99401599dc4f43ec > # Parent

Re: Does chg need to be its own program?

I think you are talking about the "entry point", which is different from "chg". At Facebook, "hg" is a wrapper that reads a tiny config file, and calls either "chg" or "hg.real", where "hg.real" is the "hg" script elsewhere. So it makes sense to have a very lightweight binary that basically

Re: Does chg need to be its own program?

Gregory Szorc writes: > Currently, chg is its own standalone C program. When invoked, it spawns a > Python/hg process (if necessary) then talks to it. > > A major disadvantage of this approach is that users need to install chg > (currently separately) and alias it to

Does chg need to be its own program?

Currently, chg is its own standalone C program. When invoked, it spawns a Python/hg process (if necessary) then talks to it. A major disadvantage of this approach is that users need to install chg (currently separately) and alias it to `hg` in their shell. This means adoption is difficult. chg

[PATCH 2 of 2] py3: fix the way we produce bytes list in store.py

# HG changeset patch # User Pulkit Goyal <7895pul...@gmail.com> # Date 1486490137 -19800 # Tue Feb 07 23:25:37 2017 +0530 # Node ID 47e72d467dd8da66092ca6b6a91235d8432e2dc1 # Parent 61c589c75ebbce625d7056297e122863b68acce9 py3: fix the way we produce bytes list in store.py bytes(range(127))

[PATCH 1 of 2] py3: convert os.__file__ to bytes

# HG changeset patch # User Pulkit Goyal <7895pul...@gmail.com> # Date 1486487844 -19800 # Tue Feb 07 22:47:24 2017 +0530 # Node ID 61c589c75ebbce625d7056297e122863b68acce9 # Parent a68510b69f413545722c086eaeb840dd5e8305b4 py3: convert os.__file__ to bytes os.__file__ returns unicode path

[PATCH STABLE] doc: update year in copyright lines

# HG changeset patch # User FUJIWARA Katsunori # Date 1486572068 -32400 # Thu Feb 09 01:41:08 2017 +0900 # Branch stable # Node ID 05b83627f1922f34680664080b22bd2b8baac91a # Parent af3b5aa61fc05a124697809bf472a5592f38489c doc: update year in copyright lines This

Re: [PATCH v2] hg: allow usage of XDG_CONFIG_HOME and $HOME/.config/hgrc

On Wed, Feb 8, 2017 at 5:01 PM, Augie Fackler wrote: > > hg: allow usage of XDG_CONFIG_HOME and $HOME/.config/hgrcThat said, pip > looks at $XDG_CONFIG_HOME/pip, so I suspect (the spec is unclear) that we > should be storing things in $XDG_CONFIG_HOME/hg - that's also

[PATCH v3] hg: allow usage of XDG_CONFIG_HOME and $HOME/.config/hg/hgrc

# HG changeset patch # User David Demelier # Date 1486485215 -3600 # Tue Feb 07 17:33:35 2017 +0100 # Node ID 5ecf752f0a79482fe2cecfa73c5a733dab29fb88 # Parent 1f51b4658f21bbb797e922d155c1046eddccf91d hg: allow usage of XDG_CONFIG_HOME and $HOME/.config/hg/hgrc

[PATCH] zeroconf: fail nicely on IPv6 only system

# HG changeset patch # User Simon Farnsworth # Date 1486570121 28800 # Wed Feb 08 08:08:41 2017 -0800 # Node ID a847eb00fcfeffce458e11b80ad38d4d4e7a700f # Parent d50cda2a403786836d1f0d5c99401599dc4f43ec zeroconf: fail nicely on IPv6 only system zeroconf only knows how to

Re: [PATCH] pager: exit cleanly on SIGPIPE (BC)

This replaces "dispatch: treat SIGPIPE as a termination signal (BC)". I'm now debugging test-paths.t, so that I can stop being acclimatised to the red failure prompt after running tests, to improve my chances of noticing this sort of issue. Simon On 08/02/2017 15:47, Simon Farnsworth wrote:

[PATCH] pager: exit cleanly on SIGPIPE (BC)

# HG changeset patch # User Simon Farnsworth # Date 1486568650 28800 # Wed Feb 08 07:44:10 2017 -0800 # Node ID d50cda2a403786836d1f0d5c99401599dc4f43ec # Parent 1f51b4658f21bbb797e922d155c1046eddccf91d pager: exit cleanly on SIGPIPE (BC) Changeset aaa751585325 removes

Re: [PATCH] dispatch: treat SIGPIPE as a termination signal (BC)

Please scrub this - it breaks `hg serve`. I'll send a v2 shortly, that moves the SIGPIPE handling into pager and thus has no BC implications. On 07/02/2017 20:08, Simon Farnsworth wrote: # HG changeset patch # User Simon Farnsworth # Date 1486498104 28800 # Tue Feb 07

[PATCH v2] hg: allow usage of XDG_CONFIG_HOME and $HOME/.config/hgrc

# HG changeset patch # User David Demelier # Date 1486485215 -3600 # Tue Feb 07 17:33:35 2017 +0100 # Node ID 880021eb7ec0be00c76739cb647e0f5712420c81 # Parent 1f51b4658f21bbb797e922d155c1046eddccf91d hg: allow usage of XDG_CONFIG_HOME and $HOME/.config/hgrc

Re: [PATCH] hg: allow usage of XDG_CONFIG_HOME and $HOME/.config/hgrc

Le 07/02/2017 à 17:52, David Demelier a écrit : # HG changeset patch # User David Demelier # Date 1486485215 -3600 # Tue Feb 07 17:33:35 2017 +0100 # Node ID 699fb7d08bdf2329fdb64df56e72d6c07cd91285 # Parent 1f51b4658f21bbb797e922d155c1046eddccf91d hg: allow

[PATCH] hg: allow usage of XDG_CONFIG_HOME and $HOME/.config/hgrc

# HG changeset patch # User David Demelier # Date 1486485215 -3600 # Tue Feb 07 17:33:35 2017 +0100 # Node ID 699fb7d08bdf2329fdb64df56e72d6c07cd91285 # Parent 1f51b4658f21bbb797e922d155c1046eddccf91d hg: allow usage of XDG_CONFIG_HOME and $HOME/.config/hgrc