DragonFly commits List (threaded) for 2008-12
DragonFly BSD
DragonFly commits List (threaded) for 2008-12
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: commit mail subject format

From: Matthias Schmidt <matthias@xxxxxxxxxxxxxxxx>
Date: Wed, 3 Dec 2008 14:32:32 +0100


* Aggelos Economopoulos wrote:
> Why do we need all this stuff in the message Subject? The "DragonFly-"
> part is essentially wasted space (gee, like I need to be reminded which
> folder I'm reading), space that could be used for something useful.

Completely agree with Aggelos.  What was wrong with the
master <files> <commit id> line?

Especially the string generated by git-describe is IMO a waste of space. What
is so special if one can see that we are n commits ahead of 2.1.1 ?

> Also, if I want any of the rest of the info, all I need is the commit id
> and I can use git to get it. Maaaybe having the commit id appended (so
> it won't intrude too much) to the Subject would be useful so you can
> speedily search for any discussions relevant to a commit, but that's
> also debatable.
> Why can't we use the commit summary or just the branch, directory and
> files changed? The whole idea behind the Subject: line is that you can
> tell at a glance if you're interested in reading the mail body and I
> don't see how this format accomplishes it... All the extra info could go
> in the message body if people still want it to be instantly available.
> Personally, I only care about the commitid and diffstat, but that's just me.
> Another idea would be to stuff the extra info in the headers so that
> each subscriber can select which fields to view, but I'd prefer a sane
> format that more or less works for everybody.

Yes, that would also be a nice solution.  A slim subject line and all special
information hidden in the header (IIRC SVN encodes the branch in a X- header).
With this solution tools like procmail can still sort the mails.



[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]