mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@suse.cz>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Brice Goglin <Brice.Goglin@ens-lyon.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux v2.6.17
Date: Mon, 19 Jun 2006 03:39:00 +0200	[thread overview]
Message-ID: <20060619013900.GD24203@pasky.or.cz> (raw)
In-Reply-To: <Pine.LNX.4.64.0606172036360.5498@g5.osdl.org>

Dear diary, on Sun, Jun 18, 2006 at 05:47:27AM CEST, I got a letter
where Linus Torvalds <torvalds@osdl.org> said that...
> 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.

I assume that this is with hot cache, which is something you shouldn't
assume for a use like this - you likely aren't in the middle of doing
stuff with the repository but just want to peek at the changes list.

Anyway, the nice thing about the Changelog files MIGHT be Google - it's
nice when googling around about your kernel problem ends up yielding
a changelog entry indicating that it's already fixed in a newer kernel
version. That is, if only Google crawled the changelogs. Does it stay
away of them because they have no extension?

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
A person is just about as big as the things that make them angry.

  reply	other threads:[~2006-06-19  2:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-18  1:59 Linus Torvalds
2006-06-18  2:06 ` Linus Torvalds
2006-06-18  3:30   ` Brice Goglin
2006-06-18  3:47     ` Linus Torvalds
2006-06-19  1:39       ` Petr Baudis [this message]
2006-06-18 13:49   ` Adrian Bunk
2006-06-18 16:44     ` Linus Torvalds
2006-06-19 21:25       ` Adrian Bunk
2006-06-19 14:23   ` Mark Lord
2006-06-18 10:54 ` Michael Buesch
2006-06-18 16:47   ` Andre Tomt
2006-06-18 17:05     ` Michael Buesch
2006-07-16 19:34 ` Linux v2.6.17 - PCI Bus hidden behind transparent bridge Julien Cristau
2006-07-17 14:13   ` Grant Grundler
2006-07-17 14:29     ` Julien Cristau
2006-07-17 15:31       ` Grant Grundler
2006-07-17 16:13         ` Julien Cristau
2006-06-19  7:41 Linux v2.6.17 linux

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060619013900.GD24203@pasky.or.cz \
    --to=pasky@suse.cz \
    --cc=Brice.Goglin@ens-lyon.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®