Actually, it turns out there is a newer wayback version of vss2cvs ... http://web.archive.org/web/20030308074752/www.laine.org/cvs/vss2cvs/ -- Mark print ("vss2cvs - SourceSafe to CVS converter.\n");
Use the wayback machine to get what you needed... http://web.archive.org/web/20010604040504/www.laine.org/cvs/vss2cvs/ There are other files in that directory such as a ReadMe.txt which you may want
[ On Saturday, March 2, 2002 at 15:34:47 (GMT), David A. Desrosiers wrote: ] What do you think the "revisions stored in the RCS" files are? The revision numbers are simply their internal identifiers.
snip.............................. ok, i think i have it. and again thanks, Mark. i've been editing and checking in a few files in the branch and all was going well until this one file. all i've samp
ok, i think i have it. and again thanks, Mark. i've been editing and checking in a few files in the branch and all was going well until this one file. all i've sampled look like: == File: RELEASENOT
Hey stop sending these information to me... Send info-cvs mailing list submissions to address@hidden To subscribe or unsubscribe via the World Wide Web, visit http://lists.nongnu.org/mailman/listinfo
Garyl, Thank you for the useful information you sent! Im tryng to follow your tip to solve the problem. But Im having dificulties to cut the revisions as the files are extense and has lot of revision
Diego, You can search for the \x3c (hex 3c?) in the rcs ,v file, which may give you a clue as to what the problem is. The ,v file format is fairly straightforward. Examine a few and you'll figure out
Excuse the cross-post. Development discussions are more appropriately sent to bug-cvs. Please delete address@hidden from any replies. Currently the command is disabled for remote access, using a quic
On Tuesday, Oct 25th 2005 at 16:51 -0200, quoth Maicon Stihler: cvs log only works in a workspace. If you're not in a workspace then use rlog. You are correct that cvs admin -o will remove revisions.
Disregard the revision numbers; they won't tell you anything that the tags won't, and can be confusing. If you have not checked anything in on branch rel-61302, then the correct revision number is 2
Thanks! (address@hidden) when the multiple_edits+reservations, ! = patch. remember 'cvs or version problem operation will that I to add versions with stdin behavior check this http://CVSHome.org ) pa
You won’t be able to commit it while it “Needs Merge”. You’ll need to run “cvs update” to merge, or erase the file and run “cvs update” again to get th
You're seeing 1.6.2.1 as your working revision because that was your working revision before you removed that branch. It looks like you committed something onto the old branch first, though, so you m
first of all, thanks for sticking with me. Einstein said that the clear definition of a problem was 90% of the solution. well that's been my problem. unable to clearly state the problem. i appreciate
Lee, It looks like your RCP_5_0_1 branch is indeed off of RCP_5_0 tag. If you look at the output from your "status" command (or a "log" command if you were to look at that), notice where it says "bra
Greg's comments generally fall under the "That's by design" category but it's not obvious that that design is good. IMHO, it is not. Directories are as first class a file system element as files are.
Hi everyboby, Well, it remembered me 2 postings from Scott Stanton on bug-cvs in october 2000. I enclose a merge of these 2 messages at the end of this posting. Best regards, Patrick Gouin. I am send
Reference: cvs-1.11.19-6mdk Disclaimer: * This is not the latest revision. A Mandriva Corporate Server 4.0 distribution is in use and this is the stock build included with it. * Use of arcanery like