Larry Jones wrote: > [EMAIL PROTECTED] writes: > > > > I know cvs recommends to ignore the versions of files and use tags, but > > why is this so hard? Here's an example that creates a new repository, > > adds a file o the trunk. Creates 2 branches 1.1.2 and 1.1.4. I update > > to 1.1.4 and add a file. Why can't the version start with 1.1.4.1 > > instead of 1.1.2.1? > > Because tags and branches are *per file* -- there's no global > information about them -- and your new file doesn't have any branches, > so how is CVS supposed to know you want to use 1.1.4?!? The revision > numbers are for CVS's internal use in organizing the files -- they are > not for your use. > > -Larry Jones > > Oh, now don't YOU start on me. -- Calvin
Ok, I created a branch tag test-1-1-4 which cvs associates with branch 1.1.4 right? So, when I add a new file, CVS tells me it is adding it on test-1-1-4, so obviously it knows I want to add it there. To me that would mean branch 1.1.4. Obviously I don't understand cvs. cvs add: scheduling file `file3' for addition on branch `test-1-1-4' Yes, I know the revision numbers are for CVS internal use, but I think it'd be nice if it were for both CVS and me. Anyways, thanks for the info and sorry for wasting bandwidth on a question asked so much. Chris _______________________________________________ Info-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/info-cvs
