summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorEric Blake <eblake@redhat.com>2012-09-11 15:26:10 -0600
committerEric Blake <eblake@redhat.com>2012-09-11 15:26:10 -0600
commitf36fadca10f2fd78997d36aff5a9651bdc750d16 (patch)
tree24999836f9934d4e2b079bbee706ecfeca868f0b /HACKING
parent984a73c0b3c7e724363148f39f44739fe98386b2 (diff)
downloadlibvirt-f36fadca10f2fd78997d36aff5a9651bdc750d16.tar.gz
build: avoid dirty docs on fresh bootstrap
* HACKING: Regenerate.
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING11
1 files changed, 6 insertions, 5 deletions
diff --git a/HACKING b/HACKING
index ab1a329085..da5e771bd3 100644
--- a/HACKING
+++ b/HACKING
@@ -36,11 +36,12 @@ Then, when you want to post your patches:
git send-email --cover-letter --no-chain-reply-to --annotate \
--to=libvir-list@redhat.com master
-(Note that the "git send-email" subcommand is usually not in the main git
-package, but part of a sub-package called "git-email".) For a single patch you
-can omit "--cover-letter", but series of a two or more patches needs a cover
-letter. If you get tired of typing "--to=libvir-list@redhat.com" designation
-you can set it in git config:
+(Note that the "git send-email" subcommand may not be in the main git package
+and using it may require installion of a separate package, for example the
+"git-email" package in Fedora.) For a single patch you can omit
+"--cover-letter", but a series of two or more patches needs a cover letter. If
+you get tired of typing "--to=libvir-list@redhat.com" designation you can set
+it in git config:
git config sendemail.to libvir-list@redhat.com