public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Diego Calleja <diegocg@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.16-rc1
Date: Thu, 19 Jan 2006 18:42:21 -0500	[thread overview]
Message-ID: <43D023DD.7000609@tmr.com> (raw)
In-Reply-To: <20060117183916.399b030f.diegocg@gmail.com>

Diego Calleja wrote:
> El Tue, 17 Jan 2006 00:19:56 -0800 (PST),
> Linus Torvalds <torvalds@osdl.org> escribió:
> 
> 
>>Anyway, it's out there now. The ShortLog is pretty readable - if you are 
>>into that kind of stuff - but as usual for an -rc1 release (which has all 
>>the frantic merging going on), it's actually too big to post on the kernel 
>>list due to the size limits. It's weighs in at 4000+ lines and 169kB.
> 
> 
> Can I ask if it's possible to "mark" new features/important changes?

New features are easy, they usually result in changes to the config 
file. You can learn a lot with "diff" that way.

However, you really need to read the patches to see what they are 
supposed to change. That's a long and thankless job, but it's a wiki, 
right? So ask a few people to just look at parts of it and write 
comments on what they see. Few for filesystems, few for networks, stuff 
like that. And a few to look at "other."

If you do all the work it's not a wiki it's a blog...
> 
> I've maintaining http://wiki.kernelnewbies.org/LinuxChanges
> for three releases and the amount of changes is so big it takes hours 
> to extract the relevant changes, adding some special string in the 
> description field could help to automate this process and make better
> changelogs.
> 
> It's not only better for me, I also know there're more people ej: man
> page maintainers looking at the full changelogs to find out if 
> something has changed. There're lot of nice things being merged on 
> each release, but there's not a way to tell people that those features 
> exist; even kernel developers don't really know what is going on in 
> other parts of the kernel. A "useful" changelog is one of the few
> things the linux kernel has been missing for ages, IMO ;)


  parent reply	other threads:[~2006-01-19 23:41 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-17  8:19 Linux 2.6.16-rc1 Linus Torvalds
2006-01-17 13:16 ` Prakash Punnoor
2006-01-17 13:36   ` Jeff Garzik
2006-01-17 13:49     ` Prakash Punnoor
2006-01-17 16:25 ` Gene Heskett
2006-01-17 18:05   ` Mauro Carvalho Chehab
2006-01-17 20:38     ` Gene Heskett
2006-01-17 17:39 ` Diego Calleja
2006-01-17 18:25   ` Linus Torvalds
2006-01-17 19:06     ` Diego Calleja
2006-01-17 20:08     ` Jan Engelhardt
2006-01-17 21:04       ` Antonio Vargas
2006-01-17 22:05         ` Jan Engelhardt
2006-01-20  8:15           ` L. A. Walsh
2006-01-20  8:28             ` David S. Miller
2006-01-20  8:47             ` Russell King
2006-01-18  0:22     ` Linux 2.6.16-rc1 -- which gcc version? Jeff Chua
2006-01-18  1:14       ` Linus Torvalds
2006-01-18  7:00       ` Arjan van de Ven
2006-01-19 23:42   ` Bill Davidsen [this message]
2006-01-17 19:27 ` Linux 2.6.16-rc1 David R
2006-01-18  4:59   ` Greg KH
2006-01-18  9:28     ` David R
2006-01-18 20:57     ` David R
2006-01-18 21:04       ` Greg KH
2006-01-17 19:54 ` Linux 2.6.16-rc1 - hrtimer hotfix Thomas Gleixner
2006-01-17 20:08   ` Lee Revell
2006-01-17 20:12     ` Thomas Gleixner
2006-01-17 21:06 ` Linux 2.6.16-rc1 Valdis.Kletnieks
2006-01-18  1:41   ` Patrick McHardy
2006-01-17 21:54 ` Eyal Lebedinsky
2006-01-17 23:27   ` Sam Ravnborg
2006-01-18  7:59     ` Jean Delvare
2006-01-18  9:15       ` Sam Ravnborg
2006-01-18 10:01         ` Kurt Wall
2006-01-18 21:10           ` Eyal Lebedinsky
2006-01-19  1:40             ` Kurt Wall
2006-01-18 11:24         ` Eyal Lebedinsky
2006-01-18 12:42           ` Sam Ravnborg
2006-01-18 12:13         ` Jean Delvare
2006-01-18 13:22         ` Jan Engelhardt
2006-01-18 18:12           ` Jean Delvare
2006-01-18 20:14             ` Jan Engelhardt
2006-01-18 20:32             ` Sam Ravnborg
2006-01-18 20:54               ` Bryan O'Sullivan
2006-01-18 21:20                 ` Sam Ravnborg
2006-01-18 21:47                   ` Bryan O'Sullivan
2006-02-07 12:42                   ` Jean Delvare
2006-02-07 16:55                     ` Bryan O'Sullivan
2006-01-18 16:15         ` Johannes Stezenbach
2006-01-18  8:44     ` Eyal Lebedinsky
2006-01-27  0:06 ` Linux 2.6.16-rc1 - usb printer problems Helge Hafting
2006-01-27 22:52   ` Greg KH

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=43D023DD.7000609@tmr.com \
    --to=davidsen@tmr.com \
    --cc=diegocg@gmail.com \
    --cc=linux-kernel@vger.kernel.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