From: Rupert Heesom <raheesom@navpoint.com>
To: linux-lvm@sistina.com
Subject: [linux-lvm] Am I patching the kernel incorrectly??
Date: 08 May 2001 08:25:01 -0400 [thread overview]
Message-ID: <989324702.3147.1.camel@localhost> (raw)
I had previously patched the kernel (stock 2.4.3) with the beta 6 patch.
Now I'm trying to update to beta 7. I tried patching the kernel is
exactly the same way as before (maybe a mistake). Most of the output is
pasted in here (at the end). I'm concerned about the prompts I got -
"Reversed (or previously applied) patch detected! Assume -R? [n]"
As you can see, I decided to reply "Y". Was that a correct assumption?
Afterwards I read the man page on "patch" and am now even less sure that
I did the right thing.
I don't want to compile the kernel modules (I have lvm as a module)
until I know that the source is in good condition.
patching file drivers/md/Makefile
Reversed (or previously applied) patch detected! Assume -R? [n] y
The next patch would delete the file drivers/md/lvm-snap.h,
which does not exist! Assume -R? [n] y
patching file drivers/md/lvm-snap.h
patching file Documentation/ioctl-number.txt
Reversed (or previously applied) patch detected! Assume -R? [n] y
Hunk #1 succeeded at 187 (offset 1 line).
--
regs
rupert
reply other threads:[~2001-05-08 12:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=989324702.3147.1.camel@localhost \
--to=raheesom@navpoint.com \
--cc=linux-lvm@sistina.com \
/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