Does anyone know how much per project flexibility we have on the format of
the "git commit" emails sent to commits@lucene ? In particular: is it
possible to ask INFRA that the branch be included in the subject, w/o that
being a massive change that affects every apache project?
ie: switch from something like...
Subject: [01/21] lucene-solr git commit: LUCENE-6835: add test case confirming
listAll is sorted; fix dir impls that weren't
...to something closer to what we had with svn...
Subject: [01/21] lucene-solr: refs/heads/jira/lucene-5438-nrt-replication git
commit: LUCENE-6835: add test case confirming listAll is sorted; fix dir impls
that weren't
?
I *love* having the first line of the commit msg in the subject now, but
it would be really nice to at a glance know when a commit was to master vs
stable vs release branch vs feature branch so i know what commits to
priorities for review.
(And folks who feel like they are getting too much mail could more easily
setup a client filter to ignore "git commit" emails that also matched
"refs/heads/jira/*" in the subject)
-Hoss
http://www.lucidworks.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
