Re: can we make the log appears in subject instead of useless sha1 ID?

[Takashi Iwai <tiwai@suse.de>]

At Wed, 18 Jun 2008 11:58:12 +0200,
Thierry Vignaud wrote:
> 
> Thierry Vignaud <tvignaud@mandriva.com> writes:
> 
> > > This is an automated email from the git hooks/update script, it was
> > > generated because a ref change was pushed to the repository.
> > > 
> > > Updating branch, master,
> > >        via  9d46f4a919532c3f29a4ca1df3a4ce4686b11f37 (commit)
> > >       from  fc5102d6c6520f48d39faf572881bc520c41aeb7 (commit)
> > > 
> > > - Log -----------------------------------------------------------------
> > > commit 9d46f4a919532c3f29a4ca1df3a4ce4686b11f37
> > > Author:     Jaroslav Kysela <perex@perex.cz>
> > > AuthorDate: Tue May 20 13:25:35 2008 +0200
> > > Commit:     Jaroslav Kysela <perex@perex.cz>
> > > CommitDate: Tue May 20 13:25:35 2008 +0200
> > > 
> > >     removed .hgtags
> > 
> > can we make the log appears in subject instead of useless sha1 ID?
> 
> I ask again if we could make the change log appears in subject instead
> of useless sha1 ID?
> 
> Current commits mails are fare less readable than previous ones (when
> using hg).  This is a regression... :-(

Oh, SHA1 ID is often more useful :)

But, yes, the current mail is often just a crap.
Do you know of any good git-commit-mail-generating script?


Takashi