From: Frank Terbeck <ft@bewatermyfriend.org>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>,
Frank Terbeck <ft@bewatermyfriend.org>
Subject: [PATCH v2 4/4] Documentation for format.coverletter and --cover-letter
Date: Mon, 4 May 2009 11:59:02 +0200 [thread overview]
Message-ID: <1241431142-8444-5-git-send-email-ft@bewatermyfriend.org> (raw)
In-Reply-To: <7v8wlxx18c.fsf@gitster.siamese.dyndns.org>
Signed-off-by: Frank Terbeck <ft@bewatermyfriend.org>
---
Documentation/config.txt | 9 +++++++++
Documentation/git-format-patch.txt | 17 ++++++++++++++---
2 files changed, 23 insertions(+), 3 deletions(-)
diff --git a/Documentation/config.txt b/Documentation/config.txt
index 5dcad94..2842cb1 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -723,6 +723,15 @@ format.attach::
value as the boundary. See the --attach option in
linkgit:git-format-patch[1].
+format.coverauto::
+ A boolean variable, if set linkgit:git-format-patch[1] will behave
+ as if it was called with its --cover-letter option, unless it was
+ run with its --stdout option.
+
+format.coverletter::
+ Configures how long a patch series needs to be for cover letters
+ to be created. The default is 2.
+
format.numbered::
A boolean which can enable or disable sequence numbers in patch
subjects. It defaults to "auto" which enables it only if there
diff --git a/Documentation/git-format-patch.txt b/Documentation/git-format-patch.txt
index 6f1fc80..64f90a1 100644
--- a/Documentation/git-format-patch.txt
+++ b/Documentation/git-format-patch.txt
@@ -19,7 +19,7 @@ SYNOPSIS
[--ignore-if-in-upstream]
[--subject-prefix=Subject-Prefix]
[--cc=<email>]
- [--cover-letter]
+ [--cover-letter[=(always|never|<length>)]]
[<common diff options>]
[ <since> | <revision range> ]
@@ -107,7 +107,11 @@ include::diff-options.txt[]
--stdout::
Print all commits to the standard output in mbox format,
- instead of creating a file for each one.
+ instead of creating a file for each one. This also disables
+ the format.coverauto option if it was set. If you really want
+ cover letters to be included in --stdout output you have to
+ specify the --cover-letter option after the --stdout option
+ on the command line.
--attach[=<boundary>]::
Create multipart/mixed attachment, the first part of
@@ -163,10 +167,17 @@ if that is not set.
to any configured headers, and may be used multiple times.
For example, --add-header="Organization: git-foo"
---cover-letter::
+--cover-letter[=(always|never|<length>)]::
In addition to the patches, generate a cover letter file
containing the shortlog and the overall diffstat. You can
fill in a description in the file before sending it out.
+ Per default, cover letters are created if a patch series is least two
+ patches long (the format.coverletter allows you to change that default
+ length). If a parameter is given it overwrites the default minimum
+ series length. If the parameter is 0 or 'never', a cover letter will
+ not be generated even if the format.coverletter option would trigger
+ normally it. If the parameter is 1 or 'always' a cover letter will
+ be generated even if the patch series is only one patch long.
--suffix=.<sfx>::
Instead of using `.patch` as the suffix for generated
--
1.6.2.2.446.gfbdc0
next prev parent reply other threads:[~2009-05-04 10:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-18 16:16 [PATCH 0/6] more automation for cover letter generation Frank Terbeck
2009-04-18 16:16 ` [PATCH 1/6] format-patch: add cover{letter,onepatch} options Frank Terbeck
2009-04-18 16:16 ` [PATCH 2/6] Add documentation for format-patch's --cover-one-patch Frank Terbeck
2009-04-18 16:16 ` [PATCH 3/6] Document format.coverletter and format.coveronepatch Frank Terbeck
2009-04-18 16:16 ` [PATCH 4/6] format-patch: introduce overwritecoverletter option Frank Terbeck
2009-04-18 16:16 ` [PATCH 5/6] Add documentation for --cover-overwrite Frank Terbeck
2009-04-18 16:16 ` [PATCH 6/6] Document format.overwritecoverletter Frank Terbeck
2009-04-18 18:31 ` [PATCH 0/6] more automation for cover letter generation Junio C Hamano
2009-05-04 9:58 ` [PATCH v2 0/4] " Frank Terbeck
2009-05-04 9:58 ` [PATCH v2 1/4] Add format.coverletter option Frank Terbeck
2009-05-04 9:59 ` [PATCH v2 2/4] Add format.coverauto boolean Frank Terbeck
2009-05-04 18:39 ` Stephen Boyd
2009-05-04 21:41 ` Frank Terbeck
2009-05-04 23:20 ` Junio C Hamano
2009-05-05 8:49 ` Frank Terbeck
2009-05-05 10:41 ` Junio C Hamano
2009-05-05 13:29 ` Frank Terbeck
2009-05-05 15:23 ` Frank Terbeck
2009-05-04 9:59 ` [PATCH v2 3/4] Add tests for coverauto, coverletter and --cover-letter Frank Terbeck
2009-05-04 9:59 ` Frank Terbeck [this message]
2009-04-21 3:32 ` [PATCH 0/6] more automation for cover letter generation Jeff King
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=1241431142-8444-5-git-send-email-ft@bewatermyfriend.org \
--to=ft@bewatermyfriend.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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;
as well as URLs for NNTP newsgroup(s).