Jeff King <p...@peff.net> writes:
> Here's a documentation patch.
> -- >8 --
> Subject: [PATCH] commit: document the temporary commit message file
> We do not document COMMIT_EDITMSG at all, but users may want
> to know about it for two reasons:
> 1. They may want to tell their editor to configure itself
> for formatting a commit message.
> 2. If a commit is aborted by an error, the user may want
> to recover the commit message they typed.
> Let's put a note in git-commit(1).
> Documentation/git-commit.txt | 9 +++++++++
> 1 file changed, 9 insertions(+)
> diff --git a/Documentation/git-commit.txt b/Documentation/git-commit.txt
> index f400835..87297dc 100644
> --- a/Documentation/git-commit.txt
> +++ b/Documentation/git-commit.txt
> @@ -407,6 +407,15 @@ This command can run `commit-msg`, `prepare-commit-msg`,
> and `post-commit` hooks. See linkgit:githooks for more
> + This file contains the commit message of a commit in progress.
> + If `git-commit` exits due to an error before creating a commit,
> + any commit message that has been provided by the user (e.g., in
> + an editor session) will be available in this file, but will be
> + overwritten by the next invocation of `git-commit`.
> SEE ALSO
Very sensible, modulo s/git-commit/git commit/ and lack of S-o-b.
I also wondered if something like the following might be useful, but
it probably falls into the "water under the bridge" category.
builtin/commit.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/builtin/commit.c b/builtin/commit.c
index 149e07d..83bcee4 100644
@@ -768,6 +768,11 @@ static int prepare_to_commit(const char *index_file, const
"with '#' will be kept; you may remove them"
" yourself if you want to.\n"
"An empty message aborts the commit.\n"));
+ status_printf(s, GIT_COLOR_NORMAL,
+ _("The file '%s' keeps a copy of the log
+ "you edited, if you wish to inspect it later.\n"
+ "It will be wiped by the next invocation of
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html