[PATCH, v3] wwwdocs: e-mail subject lines for contributions

Andrew Stubbs ams@codesourcery.com
Tue Feb 4 10:41:00 GMT 2020


On 03/02/2020 18:09, Michael Matz wrote:
> But suggesting that using the subject line for tagging is recommended can
> lead to subjects like
> 
>   [PATCH][GCC][Foo][component] Fix foo component bootstrap failure
> 
> in an e-mail directed to gcc-patches@gcc.gnu.org (from somewhen last year,
> where Foo/foo was an architecture; I'm really not trying to single out the
> author).  That is, _none_ of the four tags carried any informational
> content.

I partially disagree with this. Certainly there's pointless redundancy 
it this example, but I'd rather have the tags with a meaningful subject 
than a generic subject with no tags.

gcc-patches is a high-volume list in which most of the content is 
outside my range of interest and/or understanding. If I stay on top of 
it then I can read all the subject lines, at least, and probably select 
a few threads to learn about something new, but if I let the list get 
away from me for even a short while then it's too much to handle.

I do have filters set up to highlight subjects for which I should pay 
attention and if people are in the habit of tagging subjects then that 
becomes much more reliable.

Conversely, the tags help me quickly decide what not to read.

I see that some people are using a "[email tag] git tag: msg" format, 
and I quite like that.

Andrew



More information about the Gcc-patches mailing list