From f36fadca10f2fd78997d36aff5a9651bdc750d16 Mon Sep 17 00:00:00 2001 From: Eric Blake Date: Tue, 11 Sep 2012 15:26:10 -0600 Subject: [PATCH] build: avoid dirty docs on fresh bootstrap * HACKING: Regenerate. --- HACKING | 11 ++++++----- 1 file 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