commit mail subject format

Peter Avalos pavalos at theshell.com
Sun Dec 7 08:49:07 PST 2008


On Sun, Dec 07, 2008 at 03:15:41PM +0100, Sascha Wildner wrote:
>
> After replacing the paths with summaries, how would someone search for  
> commits to certain files using only his mail/news client?
>

Ugh. Why would they do that? I don't think this is something we should
try to support when git does a MUCH better job.

> Full text search? Hmm, not possible using NNTP unless you download all  
> articles. Use gitweb or search the repo? Well not all of us read the  
> mailing lists on the same box (or platform even) where they keep the  
> repo. And having to keep an additional window open just to see what was  
> changed doesn't seem like an improvement for me, personally.
>

But your argument was for people to search for commits to certain files
using a mail client.  This seems really silly to me.

If someone is interested the subject of a commit, they can open the
email and see which files were changed in the diffstat.  This is so much
more logical than the other way around.

> Summaries are sub-optimal for the Subject since they are human generated  
> and humans make spelling errors, might forget the  
> commit-structuring-rules and tend to formulate things differently from  
> what the guy who is searching might expect. I can understand that it  
> sounds like a good thing, but I fear that daily practice will not live  
> up to it.
>

This is easy though.  Hell, it's already mentioned in committer(7).

--Peter
Attachment:
pgp00002.pgp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pgp00002.pgp
Type: application/octet-stream
Size: 197 bytes
Desc: "Description: PGP signature"
URL: <http://lists.dragonflybsd.org/pipermail/commits/attachments/20081207/7b1088c8/attachment-0017.obj>


More information about the Commits mailing list