| commit | b2475703d8c95b39e9a05b4d5638452bacfc2a8b | |
| author | Frank Lichtenheld <frank@lichtenheld.de> | |
| Thu, 12 Apr 2007 14:54:28 +0000 (12 16:54 +0200) | ||
| committer | Junio C Hamano <junkio@cox.net> | |
| Thu, 12 Apr 2007 23:22:34 +0000 (12 16:22 -0700) | ||
| tree | aea45e6dee23ec92fcd65de6f3004e5c275fc1e8 | treesnapshot (tar.gz zip) |
| parent | 0f76a543e398b116882a49fc115273988cc9eb29 | commitdiff |
cvsserver: Document the GIT branches -> CVS modules mapping more prominently
Add a note about the branches -> modules mapping to LIMITATIONS because
I really think it should be noted there and not just at the end of
the installation step-by-step HOWTO.
I used "git branches" there and changed "heads" to "branches" in
my section about database configuration. I'm reluctant to replace
all occourences of "head" with "branch" though because you always
have to say "git branch" because CVS also has the concept of
branches. You can say "head" though, because there is no such
concept in CVS. In all the existing occourences of head other than
the one I changed I think "head" flows better in the text.
Signed-off-by: Frank Lichtenheld <frank@lichtenheld.de>
Signed-off-by: Junio C Hamano <junkio@cox.net>
Add a note about the branches -> modules mapping to LIMITATIONS because
I really think it should be noted there and not just at the end of
the installation step-by-step HOWTO.
I used "git branches" there and changed "heads" to "branches" in
my section about database configuration. I'm reluctant to replace
all occourences of "head" with "branch" though because you always
have to say "git branch" because CVS also has the concept of
branches. You can say "head" though, because there is no such
concept in CVS. In all the existing occourences of head other than
the one I changed I think "head" flows better in the text.
Signed-off-by: Frank Lichtenheld <frank@lichtenheld.de>
Signed-off-by: Junio C Hamano <junkio@cox.net>
| Documentation/git-cvsserver.txt | diffblobblamehistory |