Re: [PATCH] cvsserver: fix legacy cvs client and branch rev issues

[Dirk Koopman <djk@tobit.co.uk>]

Frank Lichtenheld wrote:

> 
> Summary: You're (ab)using cvsserver in very interesting ways that are not
> really beeing thought of in the current design/implementation. There'll
> be dragons ;)
> 

Hmm... I think that is becoming clear. The trouble is that I am not at 
all certain that what I am doing is particularly unusual. After all, 
using git, the whole point is that working on branches or the main line 
should easy and cheap!

If it were me, I might have been inclined to always set Repository to 
'master' (or even to the name of the repository with .git removed), then 
git checkout <tag> <file> each file, one at a time, using the (<tag> || 
'master') from each Entry that is sent. So with no tag, you get the 
master copy, otherwise the <tag>ged copy - this all assuming that the 
git repo is set up correctly.

But as I am CVS read only, what is there does for me so I am not 
complaining :-) The two people that can also commit can start to use git 
and send me patches... Do them good :-)

Dirk