mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.22 released
Date: Tue, 10 Jul 2007 15:39:51 -0400	[thread overview]
Message-ID: <25865.1184096391@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Sun, 08 Jul 2007 16:52:52 PDT." <alpine.LFD.0.999.0707081639370.31544@woody.linux-foundation.org>

[-- Attachment #1: Type: text/plain, Size: 1451 bytes --]

On Sun, 08 Jul 2007 16:52:52 PDT, Linus Torvalds said:

> The full changelog since 2.6.21 also got uploaded, but quite frankly, I 
> wonder if anybody uses those things? I've been uploading them for non-git 
> users, but I have a suspicion that any people who want that kind of 
> detail have long since learnt to use git, or are following the commit 
> mailing lists or equivalent. 

What the Rest Of The World could probably use is if some kind soul were to go
through and build a .21->.22 document that lists all the *userspace visible*
changes (new drivers, new filesystems/features, new/changed stuff in /sys and
/proc, new ioctls, new and changed Kconfig, etc).  Unfortunately, it's quite
probably not automagically creatable, so we'd need to find another Adrian Bunk
to do it (BTW, between cleanups and keeping track of regressions and so on,
Adrian is definitely a resource we're lucky to have - let's have a round of
applause and appreciation for all of Adrian's work.. :)

> Or do people really want the full logs, and don't use git?

I'm not really a git user (I have enough trouble keeping a -mm tree around in
an unbusticated state) - but the few times I've needed info from git, I've
gotten it from the git-web interface.  I think I've only looked at the
Changelogs once in the last 5 years, and it was because I was researching a
"When did feature XYZ go into the kernel?" for something that happened before
the bitkeeper and git days.

[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

  parent reply	other threads:[~2007-07-10 19:40 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-08 23:52 Linus Torvalds
2007-07-09  0:19 ` Jesper Juhl
2007-07-09  1:08 ` Phil Oester
2007-07-09  6:06   ` Jan De Luyck
2007-07-09  5:00 ` Willy Tarreau
2007-07-09 10:14 ` Alan Cox
2007-07-10 18:41   ` Chuck Ebbert
2007-07-09 10:30 ` Jan Engelhardt
2007-07-09 11:45   ` Jan Engelhardt
2007-07-09 14:25 ` Michal Piotrowski
2007-07-10  7:17 ` Stefano Rivoir
2007-07-10  8:52   ` Andrew Morton
2007-07-10 15:39   ` Linus Torvalds
2007-07-10 15:59     ` Stefan Richter
2007-07-11  6:38     ` Stefano Rivoir
2007-07-11  7:05       ` Linus Torvalds
2007-07-11 10:55         ` Stephen Frost
2007-07-11 14:28           ` Stefano Rivoir
2007-07-11 12:35       ` Martin Orr
2007-07-11 14:27         ` Stefano Rivoir
2007-07-11 13:10       ` Andi Kleen
2007-07-11 17:51         ` Martin Orr
2007-07-11 18:01           ` Linus Torvalds
2007-07-11 21:00             ` Martin Orr
2007-07-11 21:29               ` Linus Torvalds
2007-07-11 22:16                 ` Andi Kleen
2007-07-11 22:33                   ` Serge Belyshev
2007-07-11 22:37                   ` Linus Torvalds
2007-07-11 22:43                     ` Andi Kleen
2007-07-11 23:56                     ` Stephen Frost
2007-07-14 15:48                   ` Martin Orr
2007-07-11 16:25       ` Theodore Tso
2007-07-10 19:39 ` Valdis.Kletnieks [this message]
2007-07-10 22:26   ` Adrian Bunk
2007-07-10 23:12     ` Stefan Richter
2007-07-11  0:00       ` Adrian Bunk
2007-07-11 10:57         ` Stefan Richter
2007-07-11  0:32       ` Valdis.Kletnieks
2007-07-11  0:01     ` david

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=25865.1184096391@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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®