[PATCH] commit: explicitly documented the existence of "last-message.txt"

[Greg Ward]

On Mon, Jul 26, 2010 at 11:45 AM, Renato Cunha <renatoc at gmail.com> wrote:
> # HG changeset patch
> # User Renato Cunha <renatoc at gmail.com>
> # Date 1280158992 10800
> # Node ID 505b7d36d5bfdaa505bc0b0016d29c93752c340f
> # Parent  c5e555e064d0ceed3a177b656a49f50890d17cfa
> commit: explicitly documented the existence of "last-message.txt"
>
> diff --git a/mercurial/commands.py b/mercurial/commands.py
> --- a/mercurial/commands.py
> +++ b/mercurial/commands.py
> @@ -727,7 +727,9 @@
>     filenames or -I/-X filters.
>
>     If no commit message is specified, the configured editor is
> -    started to prompt you for a message.
> +    started to prompt you for one, and in case your commit fails,
> +    you can find a backup of your message in
> +    <repo-root>/.hg/last-message.txt.

+1, but that's a bit of a long sentence.  How about:

   If no commit message is specified, Mercurial starts your configured editor
   where you can enter a message.  In case your commit fails, you will find
   a backup of your message in ``.hg/last-message.txt``.

I took the liberty of changing passive voice to active, and I think
<repo-root> is perhaps unnecessary.  Adjust as you see fit!

Greg