From: Bryn M. Reeves <breeves@redhat.com>
To: lvm-devel@redhat.com
Subject: Posting a patch
Date: Thu, 20 Mar 2008 13:45:12 +0000 [thread overview]
Message-ID: <47E26A68.1040202@redhat.com> (raw)
In-Reply-To: <A78DB34D00374344A0AB65B6523C05DC02CDD316@marsden.win.datacash.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Gerrard Geldenhuis wrote:
> I have written a small patch for the man page lvm.8 that I want to
> submit. However I am unsure whether I should be creating a diff with cvs
> or diff and then if I use either what type of diff needs to be
> submitted.
Hi Gerrard,
You can generate the patch either way - whichever you prefer. Either one
should be generated in unified diff format (-u). When I am taking
patches from CVS I normally do:
cd ~/cvs/LVM2
cvs diff -up 2>/dev/null > the.patch
The "-p" causes the diff to include the declaration for the function
being changed - very handy for patches to .c files but probably not
necessary for a man page patch.
Otherwise, I'd do something like:
cd LVM2/
diff -Nurp man/lvm.8.orig man/lvm.8 > the.patch
Again, the -Nrp options probably aren't needed for a man page patch but
that's what I use for generating most of my patches.
Regards,
Bryn.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFH4mpo6YSQoMYUY94RAibJAKDJq84LVcWj6EzgC8/PkzZAET7tJACfSBlD
tajy6BSeCkM1F+sM2LSsNyM=
=6w4B
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-03-20 13:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 13:49 Posting a patch Gerrard Geldenhuis
2008-03-20 13:45 ` Bryn M. Reeves [this message]
2008-03-20 14:13 ` Gerrard Geldenhuis
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=47E26A68.1040202@redhat.com \
--to=breeves@redhat.com \
--cc=lvm-devel@redhat.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 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.