On Fri, 8 Feb 2008, Paul Mackerras wrote:
>
> From: Tony Breeds <[EMAIL PROTECTED]>
>
> Commit ad7f71674ad7c3c4467e48f6ab9e85516dae2720 corrected the clock
> ..
Please, when mentioning hex numbers, also do the one-liner shortlog.
I realize that in gitk (or even just with two terminal windows open and a
git repository) it's trivial to just follow the link and see what that
commit was, but even you're just doing a "git log" or more commonly if you
read the commit log somewhere else (like a mail gateway that posts them
automatically when I apply things), it's really much more readable if you
were to say something like:
Commit ad7f71674ad7c3c4467e48f6ab9e85516dae2720 ("[POWERPC] Use a
sensible default for clock_getres() in the VDSO") corrected the clock
...
which reads much mroe naturally without having to go wonder what that
commit was doing. No?
As it is, I'm pretty used to editing those things in (I do it all the
time), and I will do so for this email too, but I want to keep bringing
this up so that I hopfully wouldn't have to do it so often. So please
write your commit messages with the specific git information available,
but without _requiring_ people to be git users to get the gist of the
matter, ok?
Linus
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
