Re: Topic descriptions

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Andy Parkins <andyparkins@...>
Cc: <git@...>
Date: Wednesday, December 6, 2006 - 6:31 pm

Andy Parkins <andyparkins@gmail.com> writes:


I think the right place to store that <anything at all>
information is per-branch configuration item.  Perhaps:

	[branch "ap/clone-origin"]
        description = we talk about what this thing does and \
        what the current status of it is.

I am unlikely to use such a thing for the "What's in" message,
though.  The part that talks about "what the current status is"
is much easier to write when I need to talk about "the current";
otherwise I'd be forced to remember to think if I need to update
the information, every time I touch topic branches.

But that description thing would be useful in gitweb, for
example.

-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Topic descriptions, Andy Parkins, (Wed Dec 6, 5:53 pm)
Re: Topic descriptions, Junio C Hamano, (Wed Dec 6, 6:31 pm)
Re: Topic descriptions, Sam Vilain, (Fri Dec 8, 9:11 pm)
Re: Topic descriptions, Martin Waitz, (Thu Dec 7, 7:55 am)
Re: Topic descriptions, Andy Parkins, (Thu Dec 7, 4:37 am)
Re: Topic descriptions, Robin Rosenberg, (Thu Dec 7, 6:45 am)
Re: Topic descriptions, Junio C Hamano, (Thu Dec 7, 5:34 am)