mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chuck Ebbert <76306.1226@compuserve.com>
To: Diego Calleja <diegocg@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@osdl.org>
Subject: How to discover new Linux features (was: Re: Linux 2.6.16-rc1)
Date: Wed, 18 Jan 2006 23:20:47 -0500	[thread overview]
Message-ID: <200601182323_MC3-1-B627-7710@compuserve.com> (raw)

In-Reply-To: <20060117183916.399b030f.diegocg@gmail.com>

On Tue, 17 Jan 2006, Diego Calleja wrote:

> Can I ask if it's possible to "mark" new features/important changes?
> 
> 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,

 One way to find new features is to use "make oldconfig".

 Say you are comparing kernels 2.6.14 and 2.6.15, trying to see what
is new.  Just do this:

 1.  Copy a .config file into your 2.6.14 directory.

 2.  Run "make oldconfig" there.  It doesn't really matter what
     answers you give so long as it runs to completion.

 3.  Copy that .config file to your 2.6.15 directory.

 4.  When you run "make oldconfig" all of the new features, drivers
     etc. will cause a prompt.

 5.  There will be some false positives if options have been renamed
     or moved around, but it's generally accurate.

-- 
Chuck
Currently reading: _Noise_ by Hal Clement

             reply	other threads:[~2006-01-19  4:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-19  4:20 Chuck Ebbert [this message]
2006-01-24  7:16 ` Alex Riesen
2006-01-24 15:13   ` Randy.Dunlap
2006-01-24 21:33     ` Alex Riesen

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=200601182323_MC3-1-B627-7710@compuserve.com \
    --to=76306.1226@compuserve.com \
    --cc=diegocg@gmail.com \
    --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®