On Nov 8, 2011, at 5:11 PM, exar...@twistedmatrix.com wrote: > On 7 Jul, 01:28 pm, p.may...@imperial.ac.uk wrote: >> On 06/07/11 20:44, exar...@twistedmatrix.com wrote: >>> Thanks for volunteering. It seems like the git mirror is well in >>> hand. >> >> If so, can someone update this: >> >> http://twistedmatrix.com/trac/wiki/GitMirror > > Apparently not. It seems the other volunteers to deal with the git > mirror haven't been able to dedicate the time necessary to this. > > Anyone new want to step up?
I should stress that the most pressing problem here is not necessarily to provide a comprehensive, elaborate, automatic mirroring setup, but rather to provide canonical, correct, convenient instructions to people who are submitting tickets for review, and who want to use git for development. Ideally these instructions would not end up knocking over our version control server, either :). Right now, patches from git users show up in a variety of states of confusion and disarray: they're either based on an incredibly ancient version of trunk, or they're on a non-master branch of some repository and they don't say that, or they include 'a/' and 'b/' prefixes (i.e. they're -p1 patches when they should be -p0 according to the submission standard). This is increasingly frustrating for me as a reviewer. I've got git installed; I don't even mind running a git command or two in the process of doing a review. But I would really like to get our submission standards straight so that the patches and branches that show up for review are something I (and others) can sensibly apply. -glyph _______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
