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
| Greg Kroah-Hartman | [PATCH 002/196] Chinese: rephrase English introduction in HOWTO |
| David Brown | Re: Linux 2.6.21-rc2 |
| James Bottomley | Re: Integration of SCST in the mainstream Linux kernel |
| Justin C. Sherrill | Re: dragonflybsd.org website link? |
git: | |
| Ben Hutchings | Re: [GIT]: Networking |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
