This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ezio.melotti
Recipients chris.jerdonek, eric.araujo, ezio.melotti, ncoghlan, pitrou, sandro.tosi, terry.reedy, tshepang
Date 2013-02-01.03:59:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1359691194.48.0.317375601725.issue14468@psf.upfronthosting.co.za>
In-reply-to
Content
> The point is to allow a manageable discussion to take place around 
> points of contention

That can be done as (possibly inline) comments on bitbucket on the individual commits.

> while making forward commit progress along the way.

I'm not sure how you intend to do that, but feel free to propose what you have in mind.  As I see it, there's a bunch of text written assuming that there is a single clone or multiple not shared clones, and all this needs to be replaced and updated.  You can probably extract a couple of chunks, but that won't make a difference IMHO.

> the current massive batch of changes makes it too unwieldy.

Maybe you are overestimating it.  It's really not so massive: it's 8 changesets, 2 just remove stuff, other 2 just move existing content without adding/removing anything (so there's nothing much to review here).  Of the remaining 4 changesets, the first only adds 85 lines, the other 3 change about 20 lines each.
History
Date User Action Args
2013-02-01 03:59:54ezio.melottisetrecipients: + ezio.melotti, terry.reedy, ncoghlan, pitrou, eric.araujo, sandro.tosi, chris.jerdonek, tshepang
2013-02-01 03:59:54ezio.melottisetmessageid: <1359691194.48.0.317375601725.issue14468@psf.upfronthosting.co.za>
2013-02-01 03:59:54ezio.melottilinkissue14468 messages
2013-02-01 03:59:54ezio.melotticreate