Date: Sat, 20 Feb 2021 14:34:36 +0800 From: "Philip Paeps" <philip@freebsd.org> To: "Daniel Ebdrup Jensen" <debdrup@FreeBSD.org> Cc: git@FreeBSD.org Subject: Re: Regarding commit notifications Message-ID: <2559B0A0-9BBF-4A52-8354-757E08381137@freebsd.org> In-Reply-To: <20210220043627.ouvbirq4n2elmjdk@nerd-thinkpad.local> References: <20210220043627.ouvbirq4n2elmjdk@nerd-thinkpad.local>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-02-20 12:36:27 (+0800), Daniel Ebdrup Jensen wrote: > I had a thought the other day, that it would be nice if the subject > message sent to src-commiters and doc-commiters (and the > branch-specific > mailing lists) included the repo in question. > > For example, a mail sent to doc-commiters looked something like this > git: <hash> - doc/main - <commit header> > > Ie. the only thing that's added is the "doc/" part. > > I already mentioned this in #gitcvt on EFnet, but jhb@ asked me to > send > it in as an email. > > jhb@ also pointed out that there are mail-headers, which I wasn't > aware > of, but I still think it would be great to have it in the subject. :) > > Naturally, this doesn't need to go to the top of the TODO list ;) This sounds very redundant. The doc commit mails already go to a separate mailing list from the src commit mailing list. And as jhb pointed out: there are X-headers in the message to tell you the repo (and more) too. The downside of this is that people reading commit mail in narrow windows will see even less of the actual subject of the commit than we see now. Philip -- Philip Paeps Senior Reality Engineer Alternative Enterprises
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2559B0A0-9BBF-4A52-8354-757E08381137>