author | Junio C Hamano <gitster@pobox.com> | |
Tue, 20 Sep 2011 22:10:08 +0000 (15:10 -0700) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Wed, 5 Oct 2011 21:51:26 +0000 (14:51 -0700) | ||
commit | b7200e839737491dfe8f0297fba54621fd7d7583 | |
tree | 2d9fc810c36bbe76729a4252bbe8bcccacdc350a | tree | snapshot |
parent | 739453a3fb74ade725243ac972f02ba1aedabdf6 | commit | diff |
branch: teach --edit-description option
Using branch.$name.description as the configuration key, give users a
place to write about what the purpose of the branch is and things like
that, so that various subsystems, e.g. "push -s", "request-pull", and
"format-patch --cover-letter", can later be taught to use this
information.
The "-m" option similar to "commit/tag" is deliberately omitted, as the
whole point of branch description is about giving descriptive information
(the name of the branch itself is a better place for information that fits
on a single-line).
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Using branch.$name.description as the configuration key, give users a
place to write about what the purpose of the branch is and things like
that, so that various subsystems, e.g. "push -s", "request-pull", and
"format-patch --cover-letter", can later be taught to use this
information.
The "-m" option similar to "commit/tag" is deliberately omitted, as the
whole point of branch description is about giving descriptive information
(the name of the branch itself is a better place for information that fits
on a single-line).
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/git-branch.txt | diff | blob | history | |
builtin/branch.c | diff | blob | history |