From: Shawn Starr <Shawn.Starr@Home.net>
To: unlisted-recipients:; (no To-header on input)@pop.zip.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: [QUESTION]: Applying patches ontop of patches (2.4.1pre7 to2.4.1pre8)
Date: Wed, 17 Jan 2001 16:16:32 -0500 [thread overview]
Message-ID: <3A660BAF.3926D757@Home.net> (raw)
In-Reply-To: <Pine.LNX.4.30.0101172130580.2313-100000@space.comunit.de>
Thanks to everyone who replied :)
Sven Koch wrote:
> On Wed, 17 Jan 2001, Shawn Starr wrote:
>
> > What is the best way to apply a patch on top of a patch already applied?
> >
> > For example, with original sources 2.4.0 i applied 2.4.1pre7 but now
> > that pre8 is out, how do i apply those new patches without having to
> > delete the whole linux dir and untar 2.4.0 again just to apply pre8?
>
> reverse the patch for 2.4.1pre7
>
> for example: cd /usr/src/linux ; zcat 2.4.1pre7.gz | patch -p1 -R
>
> after that apply pre8
>
> c'ya
> sven
>
> --
>
> The Internet treats censorship as a routing problem, and routes around it.
> (John Gilmore on http://www.cygnus.com/~gnu/)
>
> -
> 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/
-
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/
next prev parent reply other threads:[~2001-01-17 21:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-17 19:34 [QUESTION]: Applying patches ontop of patches (2.4.1pre7 to 2.4.1pre8) Shawn Starr
2001-01-17 20:32 ` Sven Koch
2001-01-17 20:46 ` Tim Waugh
2001-01-17 21:16 ` Shawn Starr [this message]
2001-01-17 20:34 ` Brian Gerst
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=3A660BAF.3926D757@Home.net \
--to=shawn.starr@home.net \
--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.