summaryrefslogtreecommitdiff
path: root/git-cvsserver.perl
diff options
context:
space:
mode:
authorFrank Lichtenheld <frank@lichtenheld.de>2007-04-12 14:54:28 (GMT)
committerJunio C Hamano <junkio@cox.net>2007-04-12 23:22:34 (GMT)
commitb2475703d8c95b39e9a05b4d5638452bacfc2a8b (patch)
treeaea45e6dee23ec92fcd65de6f3004e5c275fc1e8 /git-cvsserver.perl
parent0f76a543e398b116882a49fc115273988cc9eb29 (diff)
downloadgit-b2475703d8c95b39e9a05b4d5638452bacfc2a8b.zip
git-b2475703d8c95b39e9a05b4d5638452bacfc2a8b.tar.gz
git-b2475703d8c95b39e9a05b4d5638452bacfc2a8b.tar.bz2
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>
Diffstat (limited to 'git-cvsserver.perl')
0 files changed, 0 insertions, 0 deletions