lkml.org 
[lkml]   [2006]   [Jun]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Linux v2.6.17


On Sat, 17 Jun 2006, Brice Goglin wrote:
>
> I guess I could use git to generate the full changelog once a new
> release and keep it for later...

Well, if you are already a git user (or willing to become one), there's no
point in even keeping it for later.

[torvalds@g5 linux]$ time git log v2.6.16..v2.6.17 > /dev/null

real 0m0.484s
user 0m0.448s
sys 0m0.036s

ie the logfile generation really is almost free. And yes, that's the
_full_ big log (all 92 _thousand_ lines of it, from the 6113 commits in
the 2.6.16->17 case) being generated in under half a second.

Doing the shortlog (which sort and group by author in perl) is only
fractionally more expensive.

The added benefit of doing it with git and generating it each time is that
then you can also ask for logs just for a specific subsystem.

I don't know of anything but git that can efficiently do things like

git log v2.6.16..v2.6.17 drivers/usb/

and it will show the log for all the commits that changed things under
drivers/usb. And yeah, that can be slightly more expensive, but usually
it's not noticeably so (history pruning at least in that case makes up for
the extra work it has to do to figure out which commits changed that
subsystem).

The point being that the dynamically generated data is often a lot more
useful and readable.

Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2009-11-18 23:46    [W:0.059 / U:8.104 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site