2009/8/3 Dirkjan Ochtman :
> So PEP 385 proposes to clean up the old branches we still have lying
> around in SVN.
>
> io-c: keep-clone?
strip - it was merged into py3k some months ago.
--
Amaury Forgeot d'Arc
___
Python-Dev mailing list
Python-Dev@pyt
On Mon, Aug 3, 2009 at 23:06, "Martin v. Löwis" wrote:
> > empty: keep-clone?
>
> I use that as a branch to tell build slaves to clean out their
> current checkouts. So keep-clone sounds right, assuming it is possible
> to target buildslaves at either clones or branches (which, IIUC, would
> be n
Dirkjan Ochtman wrote:
>
> okkoto-sizeof
strip - It's an 2008 Google Summer of Code project. The important changes have
been applied in r63856.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscr
On Mon, Aug 03, 2009 at 12:51:36PM +0200, Dirkjan Ochtman wrote:
> amk-mailbox: keep-clone?
strip -- this branch was for working on a fix for
http://bugs.python.org/issue1599254, but the actual work in the branch
is available as the patches attached to that item.
--amk
___
Dirkjan Ochtman wrote:
> On Tue, Aug 4, 2009 at 08:06, "Martin v. Löwis" wrote:
>> I don't know what your plan is wrt. release tags, i.e. whether you
>> want to keep them all. If you are stripping out some of the branches,
>> but plan to keep the release tags, I wonder what the tags look like.
>
>
Comments on some of the branches I've had involvement with...
On Mon, Aug 3, 2009 at 11:51 AM, Dirkjan Ochtman wrote:
> py3k-short-float-repr: strip streamed-merge
Sounds fine.
> py3k-issue1717: keep-clone
I don't think there's any need to keep this branch; its contents were
all merged (in pi
On Tue, Aug 4, 2009 at 08:06, "Martin v. Löwis" wrote:
> I use that as a branch to tell build slaves to clean out their
> current checkouts. So keep-clone sounds right, assuming it is possible
> to target buildslaves at either clones or branches (which, IIUC, would
> be necessary anyway, since we a
> empty: keep-clone?
I use that as a branch to tell build slaves to clean out their
current checkouts. So keep-clone sounds right, assuming it is possible
to target buildslaves at either clones or branches (which, IIUC, would
be necessary anyway, since we are using a mix of branches and clones).
