Linus Torvalds <torvalds@xxxxxxxx> writes:
> On Sun, 26 Nov 2006, Junio C Hamano wrote:
>>
>> This implements an experimental "git log-fpc" command that shows
>> short-log style output sorted by topics.
>>
>> A "topic" is identified by going through the first-parent
>> chains; this ignores the fast-forward case, but for a top-level
>> integrator it often is good enough.
>
> Umm. May I suggest that you try this with the kernel repo too..
Have you?
I've compared
gitk HEAD~40..HEAD
and
git-log-fpc --no-merges HEAD~40..HEAD
Admittedly, the first group ("from the tip of the master") tends
to be seriously mixed up without a fixed theme (well the theme
appears to be "fix trivial warnings and compilation breakages
not limited to any particular subsystem"), but I find the other
groups quite a sane representation of what actually happened.
My copy of your tree is a bit old (HEAD is at 1abbfb412), but I
see:
- a two-commit series on MIPS via Ralf Baechle,
- a four-commit series on ARM via Russel King,
- a three-commit series on POWERPC via Paul Mackerras,
- a seventeen-commit series in net/ area via Dave Miller,
- a three-commit series on x86_64 via Andi Kleen.
...
As you said, committer would be a good addition to break a
fast-forward case to make it even better.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html