mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.66-bk12 causes "rpm" errors
Date: Sun, 6 Apr 2003 18:28:15 -0700	[thread overview]
Message-ID: <20030406182815.65dd9304.akpm@digeo.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0304062200570.1604-100000@localhost.localdomain>

"Robert P. J. Day" <rpjday@mindspring.com> wrote:
>
> > The only change which comes to mind is the below one.  Could you do a
> > patch -R of this and retest?
> 
> ... patch deleted ...
> 
> that fixed it, but i only this second noticed the "-R" for reversing
> the patch.  i applied it normally against my 2.5.66-bk12 tree, and
> it apparently applied cleanly.  
> 
> wouldn't that suggest that that patch wasn't in my tree in the first
> place?  i'm sure i'm up to bk12 at this point.
> 

I am now very confused.

That patch _is_ in 2.5.66-bk12.  If a `patch -R' of that patch made bk12 work
correctly then the patch was the source of the changed behaviour.

Please start again ;)

Test 2.5.66, then 2.5.66-bk12, then 2.5.66-bk12 with a `patch -R' of
the patch which I sent in the earlier email.

Thanks again.

  reply	other threads:[~2003-04-07  2:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-07  1:18 Robert P. J. Day
2003-04-07  1:32 ` Andrew Morton
2003-04-07  1:41   ` Robert Love
2003-04-07  1:47     ` Robert Love
2003-04-07 11:45       ` Alan Cox
2003-04-07 14:53         ` Robert Love
2003-04-07 14:17           ` Alan Cox
2003-04-07  1:49     ` Robert Love
2003-04-07  2:59       ` J Sloan
2003-04-07 12:07     ` Robert P. J. Day
2003-04-07  2:04   ` Robert P. J. Day
2003-04-07  1:28     ` Andrew Morton [this message]
2003-04-07  3:15       ` Robert Love
2003-04-07  3:19         ` Robert Love
2003-04-07  3:29         ` Andrew Morton
2003-04-07  3:35           ` Robert Love
2003-04-07  9:05 ` Felipe Alfaro Solana
2004-04-20  8:10 Fred Shaul

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=20030406182815.65dd9304.akpm@digeo.com \
    --to=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpjday@mindspring.com \
    /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®