Daniel Berlin wrote:
No, I don't think it is a show stopper, but it is a drawback.
Then you are correct, the only way to do what you want is export, or cp
excluding the .svn directories.
Do you consider this a show stopper, or are you willing to export your
trees?
The plan is to have the regression tester find out the current head revision, and
then export this, and stash away the version number used. I should then be
able to do a checkout of selected files / subtrees if and when it is needed.
I don't know how well the server will take the extra load, but I wouldn't expect
it to be a major problem.
I also consider this to be a drawback in terms of ease of use, however, not as
bad as the missing ability in CVS to copy / rename files while keeping the
history.
Because if it's a show stopper, then so will be arch, monotone, or anyActually, having one copy of the entire repository might be cheaper than having
of our other replacements (they all either store the entire repo on your
disk, or have stuff in the working copy), and we will be stuck with cvs
until everyone is happy to use up double/whatever disk.
several dozen double checkouts. But then, having no firm, easily memorized
revision numbers is certainly a much larger issue. I understand that distributed
revision control systems would make it much harder to refer to a particular
version.
