Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to email@example.com.
Tony Hoyle wrote: > No, but the cause of it was the lack of checking for an existing > vendor tag. Import still isn't particularly error checked but it's > harder to stuff things up now (I just realised the release tags aren't > checked either). I really don't think you should forbid using the same vendor branch twice. This would seriously limit usability of the Import command (I would probably just have to stop using it - which would be a shame as it is currently saving me a lot of tedious work). Forbidding to use the same release tag twice, especially if it is indeed an existing branch (if I understood your last comments correctly you could currently not determine this? AFAICT this info is already in the RCS file, isn't it?), now that is something I could only wholeheartedly agree with from bitter experience. > Tags really need types (as well as dates and descriptions..). all > things to add at some point I guess. Agreed. >>Sure but I should still be able to import to the same branch shouldn't >>I? As I said before, I do exactly this about once a week, last time two >>days ago using CVSNT 2.0.30 and it did not try to stop me from doing so. > > Not sure how, as the code has been there for a while... Are you sure you are not confusing something? If you really did anything like that (i.e. forbidding multiple imports to the same vendor branch) it would make absolutely no sense IMHO... Cheers, -- Oliver ------ In everybody's best interest, please do not post or CC technical questions to me in private unless they are specifically about a macro/product of mine that is NOT already bundled with WinCvs. I will generally forward my replies to such posts to the CVSGUI list without further notice. ---- ------------------ JID: ogiesen at jabber.org ICQ: 18777742 (http://wwp.icq.com/18777742)