From: Adrian Bunk <bunk@stusta.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux v2.6.17
Date: Sun, 18 Jun 2006 15:49:37 +0200 [thread overview]
Message-ID: <20060618134937.GA21463@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0606171902040.5498@g5.osdl.org>
On Sat, Jun 17, 2006 at 07:06:17PM -0700, Linus Torvalds wrote:
>
>
> On Sat, 17 Jun 2006, Linus Torvalds wrote:
> >
> > Not a lot of changes since the last -rc, the bulk is actually some
> > last-minute MIPS updates and s390 futex changes, the rest tend to be
> > various very small fixes that trickled in over the last week.
>
> Btw, one thing that I was planning to ask people - does anybody find the
> full-format ChangeLog's that I produce at all useful?
>
> You can get the exact same information directly from git, and the full
> changelog (as opposed to the shortlog) tends to be pretty rough to read,
> so I suspect that most people who do want to delve into the details are
> actually much more likely to look it up using git instead (at which point
> you can obviously get much better information - graphical history, diffs,
> etc)
>
> I'm not going to stop doing the incremental shortlogs, since those are
> easy to read and I usually post them with the release announcement unless
> they end up being too large (usually -rc1 has a _lot_ of changes as a
> result of the merge window), but I'm just wondering if anybody finds the
> full logs useful at all?
>
> They're easy for me to generate, but if nobody uses them, I don't see much
> of a point..
I like to read the shortlog for getting an overview of the changes
containing a bit more detail than your verbal summary at the top.
I need git for getting more detail and I could generate them myself. But
if it wasn't there, I might not generate it myself, and might therefore
not ask "Why did this patch get into -rc6?" or become curious enough for
using git to check the contents of a commit.
> Linus
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-06-18 13:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-18 1:59 Linux v2.6.17 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
2006-06-18 13:49 ` Adrian Bunk [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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=20060618134937.GA21463@stusta.de \
--to=bunk@stusta.de \
--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