On Fri, Sep 21, 2012 at 2:51 PM, Nick Wellnhofer <[email protected]> wrote: > We should also decide on the commit email subject format. My proposal is > > [$repo/$branch] $subject
I like that better than all of the canned alternatives. Including the branch name is a great idea. :) So, an email to [email protected] would have a subject something like this: [lucy-commits] [lucy/LUCY-215-cf-extensions] Document new params It bothers me a bit that the most salient info is off on the right where it's in danger of getting truncated in many situations. How about we put the $subject earlier, and dispense with $repo? $subject [$branch] Sample: [lucy-commits] Document new params [LUCY-215-cf-extensions] Also note: Gmail does not consider text within brackets in subjects when deciding whether an email belongs to a "conversation". I'm not clear on whether this will cause weird threading when commits are merged from a feature branch to master. > From what I can tell, the overall process is: > > * Open INFRA ticket requesting migration to Git > * INFRA will then > * Switch SVN to read-only > * Create Git read-only repo at git-wip-us.apache.org > * Check that Git repo is OK > * INFRA will then > * Make Git repo writable > * Make SVN writable for the website content which will > remain under SVN > > This means that there will be no commit access for a couple of days. > > My plan is to open the INFRA ticket later next week. I'll post any updates > to lucy-dev. Nick++ Marvin Humphrey
