+1 for keeping the repo name but perhaps we could drop the "git: " prefix?
Without the prefix the subject would still be fairly distinguishable from the "svn commit" emails such as "svn commit: r1731559 - /lucene/cms/trunk/content/extpaths.txt" (assuming the svn commit emails keep their existing format). Christine ----- Original Message ----- From: dev@lucene.apache.org To: dev@lucene.apache.org At: Feb 20 2016 11:23:25 > "git: %(repo_name)s:%(shortbranch)s: %(subject)s" Looks good to me. I'd keep the repo name regardless of whether it's the main repo or not. Dawid On Sat, Feb 20, 2016 at 4:54 AM, Shawn Heisey <apa...@elyograg.org> wrote: > On 2/19/2016 6:04 PM, Ryan Ernst wrote: >> >> This sounds good, but isn't the repo name redundant given it is >> implied by the email going to commits@l.a.o? >> > > Right now, I think the only git repository we've got is lucene-solr, but > we also receive commit emails from the subversion repository that holds > the Lucene and Solr websites. That repository will probably also be > converted to git eventually. > > What would be really nice is to have the repo name removed if it's the > main code repository (lucene-solr in our case) and kept if it's > something else, but as Hoss mentioned, Infra probably will not be > willing to handle a lot of customization to the script that sends these > messages. There is probably more configurability than they *want* to > support already. > > Thanks, > Shawn > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
