public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Coywolf Qi Hunt <coywolf@gmail.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: readme-update-from-the-stone-age.patch added to -mm tree
Date: Thu, 22 Sep 2005 08:36:48 +0800	[thread overview]
Message-ID: <2cd57c900509211736414cea32@mail.gmail.com> (raw)
In-Reply-To: <200509211630.33242.blaisorblade@yahoo.it>

On 9/21/05, Blaisorblade <blaisorblade@yahoo.it> wrote:
> On Wednesday 21 September 2005 04:15, Coywolf Qi Hunt wrote:
> > On 9/21/05, akpm@osdl.org <akpm@osdl.org> wrote:
> > > The patch titled
> > >
> > >      README update from the stone age
> > >
> > > has been added to the -mm tree.  Its filename is
> > >
> > >      readme-update-from-the-stone-age.patch
> > >
> > >
>
> > > @@ -199,6 +199,9 @@ COMPILING the kernel:
> > >     are installing a new kernel with the same version number as your
> > >     working kernel, make a backup of your modules directory before you
> > >     do a "make modules_install".
> > > +   In alternative, before compiling, edit your Makefile and change the
> > > +   "EXTRAVERSION" line - its content is appended to the regular kernel
> > > +   version.
>
> > This is wrong. You expect users to both do menuconfig and edit top
> > Makefile manually?  What is the local version for then?
> Ok, yes, feel free to upgrade this to the use of CONFIG_LOCALVERSION. Or I can
> do it as well.
> --

CONFIG_LOCALVERSION is for normal users while "EXTRAVERSION" is for
developers to maintain different kernel trees.
--
Coywolf Qi Hunt
http://sosdg.org/~coywolf/

  reply	other threads:[~2005-09-22  0:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200509202336.j8KNak00013479@shell0.pdx.osdl.net>
2005-09-21  2:15 ` readme-update-from-the-stone-age.patch added to -mm tree Coywolf Qi Hunt
2005-09-21 14:30   ` Blaisorblade
2005-09-22  0:36     ` Coywolf Qi Hunt [this message]
2005-09-22 20:27       ` Blaisorblade

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=2cd57c900509211736414cea32@mail.gmail.com \
    --to=coywolf@gmail.com \
    --cc=akpm@osdl.org \
    --cc=blaisorblade@yahoo.it \
    --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