Jeff King <peff@peff.net> writes:Well, one problem is that there simply _is_ no part of the documentation where such an explanation would have a place. It does not fit in the man pages of git-branch/git-commit, it has some passing relation to the repository layout explanation (even though the latter should not be something that the user has to read and understand for basic operation), it may have some place in the user manual, but may be a bit technical/long for that. Or one places it into another isolated file and hopes that a user will stumble across it when in need of the information. Hm. Probably the usermanual is the best option in the current scheme of things. Thanks. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum - 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 |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Andrew Morton | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
| Greg KH | Re: [AppArmor 39/45] AppArmor: Profile loading and manipulation, pathname matching |
git: | |
| Gerrit Renker | [PATCH 03/37] dccp: List management for new feature negotiation |
| Arjan van de Ven | Re: [GIT]: Networking |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Jarek Poplawski | Re: [BUG] New Kernel Bugs |
