Re: gitweb kinda stopped?

[James Cloos <cloos@jhcloos.com>]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Are the commit messages regular enough to make this worthwhile?  I mean,
> the commit messages from a single project are regular, but is a commit
> message from Gnus git likely to be parsed correctly by something that
> parses messages from (say) Linux kernel git?

The format I described, namedly:

commit 0a18e15598274b79ce14342ce0bfb76a87dadb45
Author: Kevin Wells <wellsk40@gmail.com>
Date:   Tue Aug 17 17:45:04 2010 -0700

is the default format of git-log(1).  (Commits which are merges will
laso have a Merge: header.)

The --pretty=email format should already be handled as it looks like an
mbox.

The default is --pretty=medium.

The --pretty=full version replaces Date: with Commit: naming the user
who committed the commit. :^)

And --pretty=fuller adds AuthorDate: and CommitDate: headers.

Oh, --pretty=raw is much more machine readable.

Sometimes the commit mail will be a summary.  Mesa does that with big
merge commits; some other projects use thier script.

But other than those summaries, I've only seen the default (--pretty=
medium) used in commit emails.

(Oh, and if the script does not already, it should use the -M -C options
to condense the report of renames and copies.)

-JimC