On Wed, Sep 14, 2011 at 9:03 PM, Matthieu Moy <Matthieu.Moy@xxxxxxxxxxxxxxx> wrote: > Michael Haggerty <mhagger@xxxxxxxxxxxx> writes: > >> I wish that one could annotate a branch (e.g., at creation) and have the >> annotation follow the branch around. This would be a useful place to >> record *why* you created the branch, your plans for it, etc. The >> annotation should be modifiable, because often a branch evolves in >> unforeseen ways during its lifetime. Anybody could read the annotation >> to get a quick idea of what kind of work is in progress. > > Would the notes mechanism be able to annotate ref names instead of > commit sha1? Speaking from someone who has few experience with git-notes, no I don't think current git-notes can do that. But similar mechanism can be added, targeting ref instead of sha-1. But the question is, is branch description local or public? Branch description sounds local to me. I just record a branch's purpose and status (the latter is more important to me). If it's local, we just need to extend ref format to store extra text in addition to SHA-1. If it's public, perhaps if we have a good way to: - convert arbitrary text to a ref (maybe just converting spaces to hyphens) - specify a ref without writing the whole ref name (reminds me of short sha-1 vs full sha-1) then we could use branch name as branch description. The default merge commit messages can be updated to convert back branch name (which is also the branch description) to human-readable text. -- Duy -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html