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 firstname.lastname@example.org.
Tony Hoyle wrote: > Interesting idea, although info at present only returns data about the > client, not the server (it doesn't even attempt to make a server > connection) Oh, so what if I put some cvs info options in the server-side cvsrc (e.g. info -c ;) )? Ah, I guess there's no harm in forbidding/ignoring that... > - if it always connected to the server it'd require you to > know how to connect to the server beforehand which kind of defeats the > point.. > > cvs info [-c|-s] <item> Good point. An option to get a combined summary of both would IMO still be useful however - though admittedly not in the case of protocols... > Listing cvswrappers, cvsignore, cvsrc should be possible. Ah yes, cvswrappers... forgot about that one... maybe even config? The one that actually sparked the idea for me however was being able to query the built-in ignore-list... > You don't need to list modules2 as the modules come out using 'cvs ls' > as available directories. Ah, didn't know that. I haven't had time to toy with modules2 yet. It was kind of a blind shot when I included it as an example... Cheers, -- Oliver ---- ------------------ JID: ogiesen at jabber.org ICQ: 18777742 (http://wwp.icq.com/18777742)