Larry Jones wrote:
Most likely, there is at least one file in each of those directoriesI have found a few files with this problem: I used the cvs graphing capability of WinCVS to look for tags instead of branches, but that was very time consuming.
where that tag is a revision tag rather than a branch tag.
I then tried this approach: a file with the branch tag set should have a cvs version number with a zero in it; one of the adminstrative numbers. I thus did this from the command line:
find . -type f -exec sh -c "cvs -q log {} | grep forv_ver1_020311-branch" \; -print 2>/dev/null |less
Which produces a list with along these lines:
./itp/build/b_wceupdate.bat
forv_ver1_020311-branch: 1.2.0.8
./itp/build/b_wceupdate2800.bat
forv_ver1_020311-branch: 1.26.0.2
A rather brutal approach, you'll agree. Anyway, the odd thing is that I have now rid this structure of files with a wrong tagging but the error still is there. I wonder: could there be files in the Attic that are screwing up my directory structure?
Furthermore: is my very-large-ax approach a good was of searching for this error? It there are files in the Attic that are acting up, how am I going to find them? Should I search on the raw RCS files in the repository instead? How do I adapt my script to do that? (I'm not fluent in RCS at all)
--
QUOYNESS (n.) The hatefullness of words like 'relionus' and 'easiephit'. (The Meaning of Liff, Douglas Adams)
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
