Re: [python-committers] Closing the 2.6 branch?

2013-10-30 Thread Nick Coghlan
On 31 Oct 2013 01:54, "Barry Warsaw" wrote: > > On Oct 31, 2013, at 01:28 AM, Nick Coghlan wrote: > > >There's a trick to get the PEP 0 generator to move the release PEP to the > >historical section, too. I'd have to look at the source code to remember > >what it is, though. > > elif pep.t

Re: [python-committers] Closing the 2.6 branch?

2013-10-30 Thread Barry Warsaw
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Oct 30, 2013, at 04:34 PM, Jesus Cea wrote: >Could I suggest to mark the branch as "closed" in Mercurial?. I still >see it in "hg heads". $ hg pull -u /me replaces the time machine keys before Guido notices they were missing. - -Barry -BEG

Re: [python-committers] Closing the 2.6 branch?

2013-10-30 Thread Barry Warsaw
On Oct 31, 2013, at 01:28 AM, Nick Coghlan wrote: >There's a trick to get the PEP 0 generator to move the release PEP to the >historical section, too. I'd have to look at the source code to remember >what it is, though. elif pep.type_ == 'Informational': # Hack until the confl

Re: [python-committers] Closing the 2.6 branch?

2013-10-30 Thread Jesus Cea
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 30/10/13 15:18, Benjamin Peterson wrote: > 2013/10/30 Barry Warsaw : >> Now that 2.6.9 is out, I wonder if there's anything we can or >> should do to the Mercurial repository to explicitly prevent >> commits to the 2.6 branch? We have we done to

Re: [python-committers] Closing the 2.6 branch?

2013-10-30 Thread Nick Coghlan
On 31 Oct 2013 00:31, Martin v. Löwis wrote: > > Am 30.10.13 15:13, schrieb Barry Warsaw: > > Now that 2.6.9 is out, I wonder if there's anything we can or > > should do to the Mercurial repository to explicitly prevent commits > > to the 2.6 branch? We have we done to older branches? > > I think

Re: [python-committers] Closing the 2.6 branch?

2013-10-30 Thread Barry Warsaw
On Oct 30, 2013, at 03:24 PM, Martin v. Löwis wrote: >I think closing the branch is just right; it's done through "hg commit >--close-branch". >In addition, I *think* we have a hook on the master that prevents >further pushes to the branch. Looks like Benjamin updated the hook but didn't close t

Re: [python-committers] Closing the 2.6 branch?

2013-10-30 Thread Martin v. Löwis
Am 30.10.13 15:13, schrieb Barry Warsaw: > Now that 2.6.9 is out, I wonder if there's anything we can or > should do to the Mercurial repository to explicitly prevent commits > to the 2.6 branch? We have we done to older branches? I think closing the branch is just right; it's done through "hg co

Re: [python-committers] Closing the 2.6 branch?

2013-10-30 Thread Barry Warsaw
On Oct 30, 2013, at 10:18 AM, Benjamin Peterson wrote: >I've now disabled pushing to the 2.6 branch. Thanks! -Barry signature.asc Description: PGP signature ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailma

Re: [python-committers] Closing the 2.6 branch?

2013-10-30 Thread Benjamin Peterson
2013/10/30 Barry Warsaw : > Now that 2.6.9 is out, I wonder if there's anything we can or should do to the > Mercurial repository to explicitly prevent commits to the 2.6 branch? We have > we done to older branches? I've now disabled pushing to the 2.6 branch. -- Regards, Benjamin ___

[python-committers] Closing the 2.6 branch?

2013-10-30 Thread Barry Warsaw
Now that 2.6.9 is out, I wonder if there's anything we can or should do to the Mercurial repository to explicitly prevent commits to the 2.6 branch? We have we done to older branches? Also, can anybody think of anything in the devguide that needs to be updated? Cheers, -Barry signature.asc Des