[PATCH 1 of 4] test-obsolete: update extension in test to actually work

[Augie Fackler]

> On May 5, 2016, at 09:48, Pierre-Yves David <pierre-yves.david at ens-lyon.org> wrote:
> 
> I've pushed patch 1 and 2 on stable (replaced the global on patch1 with a weak ref)
> 
> Patches 4 is pushed on default (with an API flag). Patch 3 waiting on a merge of stable into default.

Should I plan to re-mail patch 3 after a merge from stable, or are you holding on to it?

> 
> On 05/05/2016 02:03 PM, Augie Fackler wrote:
>> 
>> 
>> On May 5, 2016 3:24 AM, "Yuya Nishihara" <yuya at tcha.org <mailto:yuya at tcha.org>> wrote:
>> >
>> > On Wed, 04 May 2016 22:56:04 -0400, Augie Fackler wrote:
>> > > # HG changeset patch
>> > > # User Augie Fackler <augie at google.com <mailto:augie at google.com>>
>> > > # Date 1462414190 14400
>> > > #      Wed May 04 22:09:50 2016 -0400
>> > > # Node ID ef75c94c7e670127b18bcfeda68f13e3247d8a07
>> > > # Parent  906a1c8a75fd8a18e43e8545eedcbe5222f84647
>> > > test-obsolete: update extension in test to actually work
>> >
>> > The series looks good to me. Should we move the first 2 patches to stable?
>> 
>> Fine with me. I debated that before sending.
>> 
>> 
>> 
>> _______________________________________________
>> Mercurial-devel mailing list
>> Mercurial-devel at mercurial-scm.org
>> https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
> 
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at mercurial-scm.org
> https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel