From: Shawn Starr <Shawn.Starr@Home.net>
To: linux-kernel@vger.kernel.org
Subject: [QUESTION]: Applying patches ontop of patches (2.4.1pre7 to 2.4.1pre8)
Date: Wed, 17 Jan 2001 14:34:50 -0500 [thread overview]
Message-ID: <3A65F3DA.7E2C8823@Home.net> (raw)
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?
thanks,
Shawn S.
-
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 reply other threads:[~2001-01-17 20:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-17 19:34 Shawn Starr [this message]
2001-01-17 20:32 ` [QUESTION]: Applying patches ontop of patches (2.4.1pre7 to 2.4.1pre8) Sven Koch
2001-01-17 20:46 ` Tim Waugh
2001-01-17 21:16 ` [QUESTION]: Applying patches ontop of patches (2.4.1pre7 to2.4.1pre8) Shawn Starr
2001-01-17 20:34 ` [QUESTION]: Applying patches ontop of patches (2.4.1pre7 to 2.4.1pre8) 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=3A65F3DA.7E2C8823@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox