From: Andrew Ardill <andrew.ardill@gmail.com>
Date: Wed, 21 Sep 2011 00:15:20 GMT
Subject: Re: [PATCH 2/3] branch: teach --edit-description option
Message-ID: <CAH5451nai988=jB8cgFcUaQZWWUyALC-tOSV_jdLX0r_2UfbPw@mail.gmail.com>
In-Reply-To: <7vty864y24.fsf_-_@alter.siamese.dyndns.org>

On 21 September 2011 09:02, Junio C Hamano <gitster@pobox.com> wrote:
> 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).

I understand your reasoning here, however is there a way to allow
setting the branch description in, for example, a script?

Additionally I can imagine it would be useful to be able to set the
branch description from another tool, what is the recommended way of
doing that? Should tools modify the config directly??

Regards,
Andrew