All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
To: git@vger.kernel.org
Cc: "Junio C Hamano" <gitster@pobox.com>,
	"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: [PATCH v2 1/5] config.txt: a few lines about branch.<name>.description
Date: Thu,  3 Jan 2013 21:03:07 +0700	[thread overview]
Message-ID: <1357221791-7496-2-git-send-email-pclouds@gmail.com> (raw)
In-Reply-To: <1357221791-7496-1-git-send-email-pclouds@gmail.com>


Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
---
 Documentation/config.txt | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/Documentation/config.txt b/Documentation/config.txt
index bf8f911..ee64846 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -735,6 +735,12 @@ branch.<name>.rebase::
 it unless you understand the implications (see linkgit:git-rebase[1]
 for details).
 
+branch.<name>.description::
+	Branch description, can be edited with
+	`git branch --edit-description`. Branch description is
+	automatically added in the format-patch cover letter or
+	request-pull summary.
+
 browser.<tool>.cmd::
 	Specify the command to invoke the specified browser. The
 	specified command is evaluated in shell with the URLs passed
-- 
1.8.0.rc2.23.g1fb49df

  reply	other threads:[~2013-01-03 14:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-03 14:03 [PATCH v2 0/5] nd/maint-branch-desc-doc reroll Nguyễn Thái Ngọc Duy
2013-01-03 14:03 ` Nguyễn Thái Ngọc Duy [this message]
2013-01-03 14:03 ` [PATCH v2 2/5] branch: delete branch description if it's empty Nguyễn Thái Ngọc Duy
2013-01-03 14:03 ` [PATCH v2 3/5] t4014: a few more tests on cover letter using branch description Nguyễn Thái Ngọc Duy
2013-01-03 14:03 ` [PATCH v2 4/5] format-patch: pick up correct branch name from symbolic ref Nguyễn Thái Ngọc Duy
2013-01-03 14:03 ` [PATCH v2 5/5] format-patch: pick up branch description when no ref is specified Nguyễn Thái Ngọc Duy
2013-01-03 15:49   ` Junio C Hamano
2013-01-03 16:16     ` [PATCH v3 " Nguyễn Thái Ngọc Duy

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=1357221791-7496-2-git-send-email-pclouds@gmail.com \
    --to=pclouds@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.