From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: Andries Brouwer <aeb@veritas.com>
Cc: Kai Germaschewski <kai@thphy.uni-duesseldorf.de>,
linux-kernel@vger.kernel.org
Subject: Re: RFC: "SubmittingPatches" text
Date: Sat, 18 Nov 2000 11:24:39 +0100 (MET) [thread overview]
Message-ID: <200011181024.LAA12946@cave.bitwizard.nl> (raw)
In-Reply-To: <20001117163716.A29847@veritas.com> from Andries Brouwer at "Nov 17, 2000 04:37:16 pm"
Andries Brouwer wrote:
> On Fri, Nov 17, 2000 at 09:30:13AM +0100, Kai Germaschewski wrote:
>
> > One question comes to my mind: Are patches supposed to be applied with
> > patch -p0 or patch -p1?
>
> Suppose the kernel tree is in /kernpath, starting with /kernpath/linux.
> Linus' patches can be applied by (cd /kernpath; patch -p0 -s < patch)
^^^^ ALSO
> while Alan's patches only work if you do
> (cd /kernpath/linux; patch -p1 -s < ../patch)
For uniformity, I would recommend that everyone generates patches that
are "Linus-style", but that when applying, you treat them as "Alan-style".
Less chances for surprises.
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* Common sense is the collection of *
****** prejudices acquired by age eighteen. -- Albert Einstein ********
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-11-18 10:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-16 21:32 RFC: "SubmittingPatches" text Jeff Garzik
2000-11-16 22:04 ` Alan Cox
2000-11-16 22:31 ` Tigran Aivazian
2000-11-17 2:22 ` Gary Lawrence Murphy
2000-11-18 10:16 ` Rogier Wolff
2000-11-18 13:36 ` Werner Almesberger
2000-11-17 4:59 ` Peter Samuelson
2000-11-17 8:30 ` Kai Germaschewski
2000-11-17 15:37 ` Andries Brouwer
2000-11-18 10:24 ` Rogier Wolff [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=200011181024.LAA12946@cave.bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=aeb@veritas.com \
--cc=kai@thphy.uni-duesseldorf.de \
--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.