All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@gentoo.org>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: James Bourne <jbourne@hardrock.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: 15 Apr 2003 08:00:17 +0200	[thread overview]
Message-ID: <1050386416.4061.31.camel@workshop.saharact.lan> (raw)
In-Reply-To: <20030414185806.GA12740@wohnheim.fh-wedel.de>

On Mon, 2003-04-14 at 20:58, 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.
> 

No, -ac[12] do not break.  Its only when you have something like
2.4.20.1 (ie. three '.' s).  


-- 
Martin Schlemmer



      parent reply	other threads:[~2003-04-15  5:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-07 12:22 Oops: ptrace fix buggy 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
2003-04-15  6:10                   ` Martin Schlemmer
2003-04-15  6:00                 ` Martin Schlemmer [this message]

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=1050386416.4061.31.camel@workshop.saharact.lan \
    --to=azarah@gentoo.org \
    --cc=brownfld@irridia.com \
    --cc=jbourne@hardrock.org \
    --cc=joern@wohnheim.fh-wedel.de \
    --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 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.