From: Tommy Reynolds <reynolds@redhat.com>
To: Anthony <aslan@ispdr.net.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Patch files
Date: Mon, 1 Oct 2001 11:32:59 -0500 [thread overview]
Message-ID: <20011001113259.7f61ab7f.reynolds@redhat.com> (raw)
In-Reply-To: <4.3.2.7.2.20011002021641.02340710@mail.ispdr.net.au>
In-Reply-To: <4.3.2.7.2.20011002021641.02340710@mail.ispdr.net.au>
Anthony <aslan@ispdr.net.au> was pleased to say:
> Hi everyone,
> I'm new to this list, and have been using Linux for just over a year now.
> I'll get straight to the point, as I think this may be a bit off-topic. I'm
> trying to apply a patch file to support a PCI printer card I've got. The
> patch file contains several patches, but only the last one is working. I'm
> prepared to try and sort it out myself, but I just need to know something
> about the patch file so I might be able to understand how it works. Can
> anyone please explain (or point me to the relevant documentation) to me
> what the following lines mean?:
>
> --- linux/include/linux/pci_ids.h.netmos Sat Sep 8 09:44:43 2001
> +++ linux/include/linux/pci_ids.h Sat Sep 8 09:44:45 2001
> @@ -1664,8 +1664,12 @@
>
> And this is from further down in the patch:
> @@ -2831,6 +2839,15 @@
>
> I'm using RedHat 7.1 with the included 2.4.2-2 kernel. Any help on this
> matter would be much appreciated.
Larry Wall's patch program uses the diff(1) program to perform the file
comparisons, so an "info diff" command is your friend. Hint: this is a context
diff.
---------------------------------------------+-----------------------------
Tommy Reynolds | mailto: <reynolds@redhat.com>
Red Hat, Inc., Embedded Development Services | Phone: +1.256.704.9286
307 Wynn Drive NW, Huntsville, AL 35805 USA | FAX: +1.236.837.3839
Senior Software Developer | Mobile: +1.919.641.2923
next prev parent reply other threads:[~2001-10-01 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-01 16:25 Anthony
2001-10-01 16:32 ` Tommy Reynolds [this message]
2001-10-02 12:42 ` jlnance
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=20011001113259.7f61ab7f.reynolds@redhat.com \
--to=reynolds@redhat.com \
--cc=aslan@ispdr.net.au \
--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
all inboxes | Powered by JetHome®