Re: FEATURE REQUEST: Comment assignment on branches
- From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
- Date
- Mar 16, 2010, 07:33 UTC
- Message-ID
- <vpq4okgd8kp.fsf@bauges.imag.fr>
- In-Reply-To
- <fabb9a1e1003152326m4d67f48bkc207ba7368cb54e4@mail.gmail.com>
Sverre Rabbelier <srabbelier@gmail.com> writes:
> Which is also why I think it would be nice if we could teach notes to > annotate branches/tags/the whole shaboodle. I really think that a > generic way to annotate something under /refs/ would be useful.
meetoo.
Today, we have .git/description which is used by gitweb (and others?) to say what the repository contains. That would be nice to have the same thing for branches. Take http://git.kernel.org/?p=git/git.git;a=summary for example: commits have a comment, tag have a comment, and branches just say:
10 hours ago man shortlog | log | tree 10 hours ago html shortlog | log | tree 22 hours ago pu shortlog | log | tree 22 hours ago next shortlog | log | tree 23 hours ago master shortlog | log | tree 2 days ago maint shortlog | log | tree 5 days ago todo shortlog | log | tree
A newbie will have a hard time understanding what "pu" means, while a one-liner saying (proposed update, may be rewound at any time) would give most of the required information. Actually, ideally, this could be a message like commit message (i.e. one-liner, blank line, and body).
(My 2 cents)
-- Matthieu Moy http://www-verimag.imag.fr/~moy/