From: "Peter Wächtler" <pwaechtler@loewe-komp.de>
To: "Elgar, Jeremy" <JElgar@ndsuk.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Applying multiple patches
Date: Tue, 04 Sep 2001 16:01:19 +0200 [thread overview]
Message-ID: <3B94DEAF.B56E9742@loewe-komp.de> (raw)
In-Reply-To: <F128989C2E99D4119C110002A507409801555FD8@topper.hrow.ndsuk.com>
"Elgar, Jeremy" wrote:
>
> Hi,
> Sorry if this is covered somewhere but I had a look last night (and asked
> various people) but came up blank.
>
> Is there a way to apply multiple patches to a source tree (if the patches
> were produced from the same base tree)
>
> The problem I have is thus, I want to apply patch-2.4.9-ac6 (I guess might
> as well do ac7 now) and the xfs patch
> but both are from a vanilla 2-4-9.
>
> Is there a standard way of doing this or is a `by hand solution`
>
> (I managed to apply the ac first then the xfs (ignoring a couple of files
> that are older in ac) but it was the config file that was messed up)
>
> Its probably quite simple but I couldn't figure it
>
Apply them in any order (perhaps starting with the bigger one).
While patch runs, it prints out diagnostic messages.
If one reads "... Hunk failed ..." it generates files like
config.in
config.in.rej
config.in.orig
Then you have to open config.in.rej look at the lines with "-" and "+"
in front and apply the patch manually to "config.in".
I would search with
/usr/src/linux# find . -name "*.rej"
and apply the above procedure to every found file, deleting the .rej
and .orig when done.
next prev parent reply other threads:[~2001-09-04 14:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-04 13:07 Applying multiple patches Elgar, Jeremy
2001-09-04 14:01 ` Peter Wächtler [this message]
2001-09-04 22:53 ` Thomas Duffy
-- strict thread matches above, loose matches on Subject: below --
2001-09-05 13:14 Elgar, Jeremy
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=3B94DEAF.B56E9742@loewe-komp.de \
--to=pwaechtler@loewe-komp.de \
--cc=JElgar@ndsuk.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox