public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Pierre Rousselet <pierre.rousselet@wanadoo.fr>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Applying 2.5.4-pre1 patch
Date: Wed, 06 Feb 2002 16:36:50 -0500	[thread overview]
Message-ID: <3C61A1F2.434717D@mandrakesoft.com> (raw)
In-Reply-To: <3C6119E2.2060504@wanadoo.fr> <3C619586.92EAED50@mandrakesoft.com> <3C619927.2020601@wanadoo.fr> <3C619C71.5D2A710F@mandrakesoft.com> <3C61A0F7.2020302@wanadoo.fr>

Pierre Rousselet wrote:
> 
> Jeff Garzik wrote:
> > Pierre Rousselet wrote:
> >
> >>Jeff Garzik wrote:
> >>
> >>>Pierre Rousselet wrote:
> >>>
> >>>
> >>>>Patching drivers/char/gameport with /dev/null doesn't work for me. What
> >>>>is the trick ?
> >>>>
> >>>>
> >>>/dev/null indicates a new, or a removed, file.
> >>>
> >>'patch -p0 < patch' is confused by this : "sure you want to delete this
> >>file ?"
> >>
> >
> > Linus's patches should be applied with -p1.
> 
> OK, it works. But you cannot use the patch-file outside of the linux
> directory.

This is normal with everybody else's patches, such as Alan's.  Linus is
just sorta catching up.


> It means also the patch-kernel script is dead.

Did you actually try patch-kernel, from inside the kernel dir?  It
appears to use 'p1' to apply patches.

	Jeff


-- 
Jeff Garzik      | "I went through my candy like hot oatmeal
Building 1024    |  through an internally-buttered weasel."
MandrakeSoft     |             - goats.com

      reply	other threads:[~2002-02-06 21:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-06 11:56 Applying 2.5.4-pre1 patch Pierre Rousselet
2002-02-06 13:17 ` Alessandro Suardi
2002-02-06 16:48   ` Alessandro Suardi
2002-02-06 20:43 ` Jeff Garzik
2002-02-06 20:59   ` Pierre Rousselet
2002-02-06 21:08     ` Brian Gerst
2002-02-06 21:13     ` Jeff Garzik
2002-02-06 21:32       ` Pierre Rousselet
2002-02-06 21:36         ` Jeff Garzik [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=3C61A1F2.434717D@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pierre.rousselet@wanadoo.fr \
    /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