[cvsnt] Re: vendor branch and import problem

Oliver Giesen ogware at gmx.net
Thu Feb 26 21:10:14 GMT 2004


> If you import a new version of the file with a different vendor name and
> release version, you will get 1.1.1.2 with branch 1.1.1 having two
symbolic
> tags and 1.1.1.2 having the new release tag.

Whoops! I wouldn't have expected this. This is probably what Tony was
talking about all the time... ?
I'd have expected this to create a new branch, say 1.1.3 or something like
that. I never tried importing with a different vendor branch than the one I
used previously so far. However, if this is the current behaviour then IMO
it would make even less sense to forbid using the same branch name as using
a different one is what actually messes up the repository....


> In summary, if I am correct about what is happening, then I would think
the
> proper syntax checking for the import command would be that the 'Vendor'
> tag must match the previous vendor tag

I think checking for "the previous" cannot easily be done with the current
design as tags and branches are not (yet) associated with timestamps. If I
could choose I would impose no restriction on the vendor branch at all and
instead let CVS create a new branch if the given branch differs from any
existing one and update the existing one if it matches.


> and the 'Release' tag must not match
> any previous release tags.

Right. That much is for sure. And not only release tags. It should not match
any existing tag at all.

Anyway, thanks a lot for sharing the results of your insightful
investigations.

Cheers,

-- 
Oliver
----  ------------------
JID:  ogiesen at jabber.org
ICQ:  18777742     (http://wwp.icq.com/18777742)




More information about the cvsnt mailing list