2013/10/30 Barry Warsaw ba...@python.org:
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,
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
On 31 Oct 2013 00:31, Martin v. Löwis mar...@v.loewis.de 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?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 30/10/13 15:18, Benjamin Peterson wrote:
2013/10/30 Barry Warsaw ba...@python.org:
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
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
-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
-BEGIN
On 31 Oct 2013 01:54, Barry Warsaw ba...@python.org 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
