public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Valdis.Kletnieks@vt.edu
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.22 released
Date: Wed, 11 Jul 2007 00:26:52 +0200	[thread overview]
Message-ID: <20070710222652.GE3492@stusta.de> (raw)
In-Reply-To: <25865.1184096391@turing-police.cc.vt.edu>

On Tue, Jul 10, 2007 at 03:39:51PM -0400, Valdis.Kletnieks@vt.edu wrote:
> 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).
>...

Already available:
  http://kernelnewbies.org/Linux_2_6_22

Credits for it go to Diego Calleja.

It's a Wiki, so if you miss anything there you can add it yourself.

It might make sense if Linus would give a link to the corresponding 
changelog there in future release announcements.

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


  reply	other threads:[~2007-07-10 22:26 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-08 23:52 Linux 2.6.22 released 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
2007-07-10 22:26   ` Adrian Bunk [this message]
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=20070710222652.GE3492@stusta.de \
    --to=bunk@stusta.de \
    --cc=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