[petsc-dev] giving an overview of a branches purpose

[Jed Brown]

Barry Smith <bsmith at mcs.anl.gov> writes:

>    When I create a branch that is intended for a major project I'd
>    like to be able to provide a few line description of its purpose
>    and plan etc. Is there a git way to do this?

No.  There is 'git branch --edit-description', which allows you to
record local notes about a branch, but those notes are only used in 'git
format-patch' and 'git request-pull'.

I've wanted branch descriptions and it is obviously something that makes
sense for bitbucket pull requests (already supported for email
requests), you currently have to retype the purpose in the pull request
form on the website.  It would be much better to edit the message in the
repository so others could get a more complete idea of what a branch was
trying to achieve.

I can propose it on the git list and see if there are other suggestions
or guidance on implementation.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130918/a1486215/attachment.sig>