On Fri, Jul 1, 2011 at 8:59 PM, Itamar Turner-Trauring email@example.com:
It would be far simpler to setup my DVCS to track JP's remote copy of my ticket's branch...then simply pull from that remote...make my changes and request he pull from me when he's ready to review. Automates the whole process quite a bit and reduces the round trip yak shaving.
Any reason you can't do this with our git or bzr mirrors?
From a fresh checkout of the Git mirror:
lvh@hayek ~/tmp/Twisted ±master » git log -1 commit 936493c676c424f459bee93270f3a2870b68e8e5 Author: exarkun exarkun@bbbe8e31-12d6-0310-92fd-ac37d47ddeeb Date: Tue Mar 29 14:00:14 2011 +0000 ------------------snipsnipsnip------------------
Yeah. Mar 29? That's not quite right, is it?
Or for that matter, you can include e.g. an github URL in the ticket instead of attaching the patch.
Only if there's a decent Github mirror to fork from, otherwise you're asking people to do a multi-hour operation (I know, because I'm doing it right now) to get a decent git repo, followed by a large push to Github, and then maybe you can start doing some work. There is a seemingly good mirror maintained by powdahound, but it's not official and as such is not recorded anywhere.