From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: James Bourne <jbourne@hardrock.org>
Cc: Martin Schlemmer <azarah@gentoo.org>,
Ken Brownfield <brownfld@irridia.com>,
Marc-Christian Petersen <m.c.p@wolk-project.de>,
KML <linux-kernel@vger.kernel.org>
Subject: Re: Oops: ptrace fix buggy
Date: Mon, 14 Apr 2003 23:41:06 +0200 [thread overview]
Message-ID: <20030414214106.GA22050@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0304141515080.24383-100000@cafe.hardrock.org>
On Mon, 14 April 2003 15:19:27 -0600, James Bourne wrote:
> On Mon, 14 Apr 2003, Jörn Engel wrote:
>
> > So basically, neither the existing EXTRAVERSION nor my new FIXLEVEL
> > are checked. Any code could potentially break with -ac1 to -ac2 or
> > with .1 to .2.
> >
> > Did anyone experience such problems with -ac already? There are far
> > more changes in -ac than there are in your patch.
>
> Which brings the point as to why use a new variable unless you are going to
> actually modify LINUX_VERSION_CODE with it. It actually makes more sense to
> just use EXTRAVERSION for this then.
>
> Now, using EXTRAVERSION = .2 wouldn't be unrealistic...
Good point. My two (weak) arguments for the new variable are:
- A fixes-only tree is imo different from any other patchset and
should be marked as such. 2.4.20.2 sounds more official than
2.4.20-jb2. Whether this should be underscored for the developers as
well - not sure.
- It makes things like 2.4.20.1-je1 easier. But then again, someone
will come up with 2.4.21-pre7-ac1-je2-something_else5-even_more.
Sound a little too weak for the extra variable. Could have been a sign
that I lost the patch.
Jörn
--
Anything that can go wrong, will.
-- Finagle's Law
next prev parent reply other threads:[~2003-04-14 21:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-07 12:22 Michael Lampe
2003-04-12 7:13 ` Ken Brownfield
2003-04-12 9:54 ` Marc-Christian Petersen
2003-04-14 13:34 ` James Bourne
2003-04-14 13:46 ` Jörn Engel
2003-04-14 13:56 ` James Bourne
2003-04-14 14:22 ` Jörn Engel
2003-04-14 14:31 ` Martin Schlemmer
2003-04-14 14:47 ` Jörn Engel
2003-04-14 17:09 ` James Bourne
2003-04-14 17:21 ` Jörn Engel
2003-04-14 18:16 ` James Bourne
2003-04-14 17:50 ` Russell King
2003-04-14 18:10 ` Martin Schlemmer
2003-04-14 18:58 ` Jörn Engel
2003-04-14 19:20 ` Valdis.Kletnieks
2003-04-14 21:19 ` James Bourne
2003-04-14 21:41 ` Jörn Engel [this message]
2003-04-15 6:10 ` Martin Schlemmer
2003-04-15 6:00 ` Martin Schlemmer
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=20030414214106.GA22050@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=azarah@gentoo.org \
--cc=brownfld@irridia.com \
--cc=jbourne@hardrock.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@wolk-project.de \
/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®