From: Mike Castle <dalgoda@ix.netcom.com>
To: linux-kernel@vger.kernel.org
Subject: Re: /proc/config idea
Date: Tue, 3 Apr 2001 12:30:14 -0700 [thread overview]
Message-ID: <20010403123014.A17132@thune.yy.com> (raw)
In-Reply-To: <3AC91800.22D66B24@mandrakesoft.com> <Pine.LNX.4.33.0104021734400.30128-100000@dlang.diginsite.com> <20010403161322.A8174@werewolf.able.es> <3ACA1A91.70401@kalifornia.com> <20010403211218.A2387@werewolf.able.es>
In-Reply-To: <20010403211218.A2387@werewolf.able.es>; from jamagallon@able.es on Tue, Apr 03, 2001 at 09:12:18PM +0200
On Tue, Apr 03, 2001 at 09:12:18PM +0200, J . A . Magallon wrote:
> Just like the Alan Cox for 2.4 or Andrea Arcangeli for 2.2. Lets say you
> have 2.4.2-ac27. For each of your compiles, set EXTRAVERSION to -ac27-bf1,
> -ac27-bf2, etc. Your files will be:
Some patches, such as the RAID patches, sets up EXTRAVERSION to a specific
value.
I do with the make file also had a USERVERSION that would be hands off for
anyone but the builder.
mrc
--
Mike Castle Life is like a clock: You can work constantly
dalgoda@ix.netcom.com and be right all the time, or not work at all
www.netcom.com/~dalgoda/ and be right at least twice a day. -- mrc
We are all of us living in the shadow of Manhattan. -- Watchmen
next prev parent reply other threads:[~2001-04-03 19:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-02 13:25 /proc/config idea Ian Soboroff
2001-04-02 14:58 ` Jeremy Jackson
2001-04-02 15:19 ` Brian Gerst
2001-04-02 15:28 ` Bart Trojanowski
2001-04-03 0:23 ` Jeff Garzik
2001-04-03 0:37 ` Jeremy Jackson
2001-04-03 0:49 ` Jeff Garzik
2001-04-03 2:52 ` David Lang
2001-04-03 11:18 ` Olaf Titz
2001-04-03 12:27 ` Alan Cox
2001-04-03 12:43 ` Jeremy Jackson
2001-04-03 14:32 ` Alan Cox
2001-04-03 0:39 ` David Lang
2001-04-03 5:56 ` Michal Jaegermann
2001-04-03 14:13 ` J . A . Magallon
2001-04-03 18:46 ` Ben Ford
2001-04-03 19:11 ` Alan Cox
2001-04-03 19:12 ` J . A . Magallon
2001-04-03 19:30 ` Mike Castle [this message]
2001-04-04 11:56 ` GOMBAS Gabor
2001-04-03 20:57 ` Ben Ford
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=20010403123014.A17132@thune.yy.com \
--to=dalgoda@ix.netcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.