2013-09-04 08:27 AEST by Arthur Barrett - It's possible for a customer to try and 'migrate' a repository by adding a repository to a repository 
therefore ending up with a mess of file.xxx,v,v files.

I wonder if 'cvs add' should have a sanity test for that.  If the file ends with ,v require a --yes-i-know-
what-im-doing flag...

It's a significant breakage though if someone actually has blah,v files...

Probably a 'good' migrate utility that pops up in the wizard is a better choice (see bug 6347).  

What I'm proposing here is a hybrid approach where the first time  you try and add a ,v file to the repo the 
wizard pops up asking if you are trying to migrate, with an option 'do not show this option again'   
Actually setting the 'do not ask again' option would prevent the cvsnt client from actually performing that 
'test' in future, not prevent the wizard running migration (eg: a manual wizard/migrate)

It just covers an extra use case.  It's a 'client only' fix, so it wouldn't prevent someone using the 'free' 
TCVS to add ,v files).

Since the wizard is windows only, this also only covers windows users.