GIT commit message format

Alex Deucher alexdeucher at gmail.com
Mon Jul 24 10:34:29 PDT 2006


On 7/24/06, Ian Romanick <idr at us.ibm.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Felix Kühling wrote:
>
> > I'm getting a bit overwhelmed with the new GIT commit messages with all
> > the diffs. I do like having the diffs, but when one message contains
> > multiple commits, it gets hard to get a quick overview of all the
> > changes. You need to scroll through the entire thing to see what's going
> > on.
> >
> > Would it be possible to have something like a table of contents at the
> > top of the message with the one-line summaries of all changes included
> > in the message? That would make it easier to decide which patches I want
> > to look at in more detail and save a lot of time on changes that aren't
> > interesting for me.
> >
> > With the current format I just stopped reading multi-commit messages
> > because it's too much of a time sink for a spare-time developer.
>
> Agreed.  It's a bit annoying even for full-time developers.

hmmm... my recent pushes only show the commit messages, but not the
diffs.  I'm not sure what I did differently.

Alex

> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2.2 (GNU/Linux)
>
> iD8DBQFExPrZX1gOwKyEAw8RAnsYAJ4w+dppE56xwHzNK0976eyw0QV1aQCgjCHW
> YdF2LshBjrS4f/GfIrakPNk=
> =wF4d
> -----END PGP SIGNATURE-----
> _______________________________________________
> xorg mailing list
> xorg at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/xorg
>



More information about the xorg mailing list