Re: [PATCH v3 rebased] pager: migrate heavily-used extension into core

Augie Fackler writes: >> On Feb 6, 2017, at 14:47, Bryan O'Sullivan wrote: >> >> # HG changeset patch >> # User Bryan O'Sullivan >> # Date 1486160890 28800 >> # Fri Feb 03 14:28:10 2017 -0800 >> # Node ID

Re: [PATCH] chg: verify XDG_RUNTIME_DIR

> On Feb 6, 2017, at 20:03, Jun Wu wrote: > > # HG changeset patch > # User Jun Wu > # Date 1486429266 28800 > # Mon Feb 06 17:01:06 2017 -0800 > # Node ID 8081cb8c346f1ccfa8c98e94d7e25cdfccafeb06 > # Parent b6c051cd1231910b0981edb01b173cd53a3338d0 > #

Re: [PATCH] check-code: permit functools.reduce

> On Feb 6, 2017, at 17:22, Yedidya Feldblum wrote: > > # HG changeset patch > # User Yedidya Feldblum > # Date 1485038593 28800 > # Sat Jan 21 14:43:13 2017 -0800 > # Node ID 47d8e895ccb734f0219dd046795b042da002b06b > # Parent

Re: [PATCH v2] pager: migrate heavily-used extension into core

> On Feb 6, 2017, at 19:26, Jun Wu wrote: > >> As a sketch of where this is headed, API-wise: >> >> class ui: >> def pager(self, command, category): > > Just to confirm if I understand correctly, command and category are only > used to find out the actual pager command from the

Re: [PATCH v3 rebased] pager: migrate heavily-used extension into core

> On Feb 6, 2017, at 14:47, Bryan O'Sullivan wrote: > > # HG changeset patch > # User Bryan O'Sullivan > # Date 1486160890 28800 > # Fri Feb 03 14:28:10 2017 -0800 > # Node ID ae22925dafd4a270cb80a7bb54c9d70bce49a633 > # Parent

[PATCH] chg: verify XDG_RUNTIME_DIR

# HG changeset patch # User Jun Wu # Date 1486429266 28800 # Mon Feb 06 17:01:06 2017 -0800 # Node ID 8081cb8c346f1ccfa8c98e94d7e25cdfccafeb06 # Parent b6c051cd1231910b0981edb01b173cd53a3338d0 # Available At https://bitbucket.org/quark-zju/hg-draft # hg pull

Re: [PATCH v2] pager: migrate heavily-used extension into core

Excerpts from Augie Fackler's message of 2017-02-06 17:52:30 -0500: > (sending again because this seems to have gotten stuck somewhere...) > (+yuya explicitly for chg thoughts, +smf so someone else can forward to the > list if it's stuck again) chg would be fine so long as ui.pager() calls

Re: [PATCH v2] pager: migrate heavily-used extension into core

Augie Fackler writes: >> On Feb 6, 2017, at 18:32, Sean Farley wrote: >> >> Augie Fackler writes: >> On Feb 6, 2017, at 18:04, Sean Farley wrote: Augie Fackler writes: > (sending

Re: [PATCH] check-code: permit functools.reduce

Yedidya Feldblum writes: > # HG changeset patch > # User Yedidya Feldblum > # Date 1485038593 28800 > # Sat Jan 21 14:43:13 2017 -0800 > # Node ID 47d8e895ccb734f0219dd046795b042da002b06b > # Parent 036c37bd3ec189480647ff568cee9e0b43a5bc81 > check-code:

Re: [PATCH v2] pager: migrate heavily-used extension into core

> On Feb 6, 2017, at 18:32, Sean Farley wrote: > > Augie Fackler writes: > >>> On Feb 6, 2017, at 18:04, Sean Farley wrote: >>> >>> Augie Fackler writes: >>> (sending again because this seems to have gotten stuck

[PATCH] check-code: permit functools.reduce

# HG changeset patch # User Yedidya Feldblum # Date 1485038593 28800 # Sat Jan 21 14:43:13 2017 -0800 # Node ID 47d8e895ccb734f0219dd046795b042da002b06b # Parent 036c37bd3ec189480647ff568cee9e0b43a5bc81 check-code: permit functools.reduce diff --git

Re: [PATCH v2] pager: migrate heavily-used extension into core

Augie Fackler writes: >> On Feb 6, 2017, at 18:04, Sean Farley wrote: >> >> Augie Fackler writes: >> >>> (sending again because this seems to have gotten stuck somewhere...) >>> (+yuya explicitly for chg thoughts, +smf so someone else can

Re: [PATCH 08 of 10 shelve-ext v3] shelve: add obs-based unshelve functionality

Kostia Balytskyi writes: > On 06/02/2017 19:41, Sean Farley wrote: > >> Kostia Balytskyi writes: >> >>> On 03/02/2017 23:17, Sean Farley wrote: >>> Kostia Balytskyi writes: > # HG changeset patch > # User Kostia

Re: [PATCH 08 of 10 shelve-ext v3] shelve: add obs-based unshelve functionality

On 06/02/2017 19:41, Sean Farley wrote: > Kostia Balytskyi writes: > >> On 03/02/2017 23:17, Sean Farley wrote: >> >>> Kostia Balytskyi writes: >>> # HG changeset patch # User Kostia Balytskyi # Date 1484835394 28800 #

Re: [PATCH v2] pager: migrate heavily-used extension into core

> On Feb 6, 2017, at 18:04, Sean Farley wrote: > > Augie Fackler writes: > >> (sending again because this seems to have gotten stuck somewhere...) >> (+yuya explicitly for chg thoughts, +smf so someone else can forward to the >> list if it's stuck again) >>

Re: [PATCH v2] pager: migrate heavily-used extension into core

Augie Fackler writes: > (sending again because this seems to have gotten stuck somewhere...) > (+yuya explicitly for chg thoughts, +smf so someone else can forward to the > list if it's stuck again) > > On Fri, Feb 03, 2017 at 04:16:09PM -0800, Bryan O'Sullivan wrote: >> # HG

Re: Gardening extensions

On Mon, Feb 6, 2017 at 1:45 PM, Kevin Bullock < kbullock+mercur...@ringworld.org> wrote: > > Both of these are still extensions because they enable history editing. I > recall discussions around moving these into core being predicated on evolve > going in first. But phases are already in core,

Re: [PATCH v2] pager: migrate heavily-used extension into core

(sending again because this seems to have gotten stuck somewhere...) (+yuya explicitly for chg thoughts, +smf so someone else can forward to the list if it's stuck again) On Fri, Feb 03, 2017 at 04:16:09PM -0800, Bryan O'Sullivan wrote: > # HG changeset patch > # User Bryan O'Sullivan

Re: Backwards compatibility before all else? [was Re: [PATCH v2] pager: migrate heavily-used extension into core]

Bryan O'Sullivan writes: > On Sun, Feb 5, 2017 at 7:24 PM, Augie Fackler wrote: > >> >> > I'm inclined to *not* add special code to see if the old pager extension >> has been disabled. That's achievable by disabling the pager instead. This >> would require

Re: Backwards compatibility before all else? [was Re: [PATCH v2] pager: migrate heavily-used extension into core]

> On Feb 6, 2017, at 14:00, Bryan O'Sullivan wrote: > > Well, this is an interesting case of a bigger pattern. > > To be honest, I think that the long-time insistence on (and acquiescence to) > backwards compatibility for every little aspect of behaviour for all eternity

Re: for 4.2 sprint, accommodations around Moutain View

Martin von Zweigbergk via Mercurial-devel writes: > On Fri, Feb 3, 2017 at 10:15 AM FUJIWARA Katsunori > wrote: > >> Hi, devels >> >> Now, I'm looking for accommodations for upcoming 4.2 sprint, and >> surprised by high price hotel fee

Re: [PATCH RFC] contrib: script to generate release notes from commit messages

Gregory Szorc writes: > On Fri, Feb 3, 2017 at 12:40 AM, Denis Laxalde > wrote: > >> Gregory Szorc a écrit : >> >>> # HG changeset patch >>> # User Gregory Szorc >>> # Date 1486108530 28800 >>> # Thu Feb 02

Re: Evolve naming troubles

Pierre-Yves David writes: > On 01/20/2017 07:11 PM, Sean Farley wrote: >> While we are in a freeze and have some time to think about things >> outside of features, I'd like to bring up naming evolution terms before >> they are permanently frozen. >> >> I'll keep

Re: Gardening extensions

> On Feb 6, 2017, at 14:44, Bryan O'Sullivan wrote: > > Not surprisingly, the pager extension isn't the only one in my sights at the > moment. > > Here are a few others I've been thinking about. > > Proposals to move into core: > > * color - approaching its tenth

Re: Gardening extensions

Bryan O'Sullivan writes: > Not surprisingly, the pager extension isn't the only one in my sights at > the moment. > > Here are a few others I've been thinking about. > > Proposals to move into core: > > * color - approaching its tenth anniversary, and widely used. Yep. > *

Gardening extensions

Not surprisingly, the pager extension isn't the only one in my sights at the moment. Here are a few others I've been thinking about. Proposals to move into core: * color - approaching its tenth anniversary, and widely used. * histedit - widely used for 5+ years. * rebase - almost a decode

Re: [PATCH] match: adding non-recursive directory matching

On Sun, Feb 5, 2017 at 4:01 AM, FUJIWARA Katsunori wrote: > At Fri, 3 Feb 2017 20:26:04 -0800, > Rodrigo Damazio wrote: > > > > [1 ] > > [1.1 ] > > Finally working on this again. > > On point which I discussed with Martin offline - which feels more > intuitive > > as a

Re: Backwards compatibility before all else? [was Re: [PATCH v2] pager: migrate heavily-used extension into core]

> On Feb 6, 2017, at 15:00, Bryan O'Sullivan wrote: > > On Sun, Feb 5, 2017 at 7:24 PM, Augie Fackler wrote: > > > I'm inclined to *not* add special code to see if the old pager extension > > has been disabled. That's achievable by disabling the pager

Backwards compatibility before all else? [was Re: [PATCH v2] pager: migrate heavily-used extension into core]

On Sun, Feb 5, 2017 at 7:24 PM, Augie Fackler wrote: > > > I'm inclined to *not* add special code to see if the old pager extension > has been disabled. That's achievable by disabling the pager instead. This > would require a release note, of course (just in case anyone reads

Re: Making chg stateful

Excerpts from Yuya Nishihara's message of 2017-02-05 13:59:32 +0900: > Perhaps that is a matter of taste, I like the explicit one. But I heard > Python 3 has a generator-based coroutine, so using "yield" for that purpose > is more common in Python 3? > > @preload('index') > def

[PATCH v3 rebased] pager: migrate heavily-used extension into core

# HG changeset patch # User Bryan O'Sullivan # Date 1486160890 28800 # Fri Feb 03 14:28:10 2017 -0800 # Node ID ae22925dafd4a270cb80a7bb54c9d70bce49a633 # Parent 1f51b4658f21bbb797e922d155c1046eddccf91d pager: migrate heavily-used extension into core No default behaviours

Re: [PATCH v2] pager: migrate heavily-used extension into core

On Mon, Feb 6, 2017 at 9:44 AM, Augie Fackler wrote: > Yes, we should definitely make pager easier to use. My own informal > surveys of users are that even a setting in hgrc would be better than an > extension, because there's a perception that an extension is somehow >

Re: [PATCH] smartset: move set classes and related functions from revset module (API)

Yuya Nishihara writes: > # HG changeset patch > # User Yuya Nishihara > # Date 1476606531 -32400 > # Sun Oct 16 17:28:51 2016 +0900 > # Node ID a555e941ebe982cc22e15670bfe125017b3121e5 > # Parent 8d7e40524ae467b3201e264e3548681c52bb6492 > smartset: move set

Re: [PATCH 2 of 2 remotenames-ext v2] lazyremotenamedict: rename resolvekeys to resolvenodes

Kostia Balytskyi writes: > # HG changeset patch > # User Kostia Balytskyi > # Date 1486377812 28800 > # Mon Feb 06 02:43:32 2017 -0800 > # Node ID b6b0363782555a9acc98c79c25aa7b1c38ece709 > # Parent f7a3dffec18438cffeef930c8e2ed4f2da0bd4bb >

Re: Google Summer of Code 2017.

> On Feb 5, 2017, at 18:45, Pulkit Goyal <7895pul...@gmail.com> wrote: > > The wiki page for Python GSoC 2017 states that interested organisations need > to apply as a sub-org before 8th Feb[1]. Taking part under the Python > Software Foundation umbrella will be good, we participated last time

Re: [PATCH v2] pager: migrate heavily-used extension into core

Excerpts from Augie Fackler's message of 2017-02-05 22:24:39 -0500: > > On Sun, Feb 5, 2017 at 1:44 AM, Yuya Nishihara wrote: > > I like the direction of this patch, but this still involves a behavior > > change. If PAGER variable is set but pager extension disabled, pager will > >

Re: [PATCH 08 of 10 shelve-ext v3] shelve: add obs-based unshelve functionality

On 03/02/2017 23:17, Sean Farley wrote: > Kostia Balytskyi writes: > >> # HG changeset patch >> # User Kostia Balytskyi >> # Date 1484835394 28800 >> # Thu Jan 19 06:16:34 2017 -0800 >> # Node ID 94a237a046059ef246aacb2c3ad809c9f0bdbe70 >> # Parent

[PATCH 2 of 2 remotenames-ext v2] lazyremotenamedict: rename resolvekeys to resolvenodes

# HG changeset patch # User Kostia Balytskyi # Date 1486377812 28800 # Mon Feb 06 02:43:32 2017 -0800 # Node ID b6b0363782555a9acc98c79c25aa7b1c38ece709 # Parent f7a3dffec18438cffeef930c8e2ed4f2da0bd4bb lazyremotenamedict: rename resolvekeys to resolvenodes I think my