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 sales@march-hare.com.
Oliver Giesen wrote: > Tony Hoyle wrote: > >> It won't return the .cvsignore files in individual directories as >> they're added on the fly during update. You also get duplicates - >> there's never been any duplicate detection on in the code as it just >> scans from top-bottom and breaks on the first hit, so if you're >> processing it automatically you'll need to do similar. > > Fine with me. Just what I expected. What I did not expect however was that it appears to _always_ return the *complete* list twice... Not that it is really a problem for my parser but it just appears a bit odd... Also, any news on this?: >> cvsrc is harder as it's not stored > > Huh? It's right next to .cvsignore isn't it? > > >> - it's just calculated based on the >> current command. > > That's why I thought it would be nice if one could (optionally) just get > the options for a given command as in: cvs info cvsrc update . > > >> As there's no builtin .cvsrc this could be implemented >> externally with a checkout + reading the one on the client side... >> that's pretty much what I'd have to do anyway :) > > Is that different from what you now do with cvsignore? Cheers, -- Oliver ---- ------------------ JID: ogiesen at jabber.org ICQ: 18777742 (http://wwp.icq.com/18777742)