From: Martin Stricker <shugal@gmx.de>
To: selinux@tycho.nsa.gov
Subject: Re: how to write and understand a patch file?
Date: Sun, 28 Mar 2004 17:37:26 +0200 [thread overview]
Message-ID: <4066F136.3DCA73D7@gmx.de> (raw)
In-Reply-To: 20040328100448.19776.qmail@web41308.mail.yahoo.com
Park Lee wrote:
>
> Hi,
> Would you please tell me how to write and understand a patch file?
> I just want to learn more about it.
You create a patch with `diff` and apply it with `patch`. A patch is
just a list of differences between the original version of a source code
file (you cannot patch a binary) and your altered version.
--
Homepage: http://www.martin-stricker.de/
Linux Migration Project: http://www.linux-migration.org/
Red Hat Linux 9 for low memory: http://www.rule-project.org/
Registered Linux user #210635: http://counter.li.org/
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2004-03-28 17:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-28 10:04 how to write and understand a patch file? Park Lee
2004-03-28 15:37 ` Martin Stricker [this message]
2004-03-28 15:46 ` Ed Street
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=4066F136.3DCA73D7@gmx.de \
--to=shugal@gmx.de \
--cc=selinux@tycho.nsa.gov \
/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.