On Apr 15, 2008, at 4:53 PM, Stephen Sinclair wrote:
On Tue, Apr 15, 2008 at 3:12 PM, Junio C Hamano <gitster@xxxxxxxxx>
wrote:
Not complicated at all. Put that description in-tree in a known
location
(say, "help-branch") in-tree and your propagation problem is solved.
And have a scriptlet in $HOME/bin/git-help-branch to grep from that
file.
Hm, I wasn't sure if an in-tree solution would be appropriate.
It's possible, but I didn't really want this branch description to be
something I have to deal with when merging..
Ideally though this information _should_ be propagated through a
clone, so something in-tree might make sense.
When I posted I thought perhaps there was already a way to do this
that I hadn't encountered.
Perhaps there could be an in-tree file .gitbranch that is simply a
name:description pair, "git-branch --info" (or whatever) could be made
to know how to parse that file if it exists.
However I was hoping that the branch description could be made when
creating the branch, instead of having to associate it with an actual
commit.
A random thought:
refs/info/heads/help is a pointer to a blob that is full of name-
description pairs. Instead of a full ref name it simply keeps the
portion for a given subdirectory. On a pull, you can add refs/info/
heads/help:refs/info/remote/origin/help. Each subdirectory of refs
gets it's own help blob. You may need to deal with merging on pull,
but it keeps the information separate from the commits and still pull/
pushable.
~~ Brian
--
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
