There is also a way to use the co command in a dry run mode (-n global
opton I believe.) Then, you just do a 'co .' and see what it would have
checked out. But all my attempts to do this on DF.net failed with a
protocal error.
And yabb in CVSROOT for SF.net didn't yeild anything, sorry. I guess the
ViewCVS investigation is the only way to go. But it might not yeild
anything, because it most likely can just read the CVS folders directly
off the hard distk. (IOW, I don't think it needs a cvs command to get at
them since most are apache on the same server as the cvs repositories.
(:pserver host.)
Ed
Robert Citek wrote:
On Aug 3, 2005, at 1:08 PM, JT Moree wrote:
Ed Howland wrote:
The only way to do this, is via the web interface to CVS:
how does the web interface find out? there must be a way. it is the
tags and branches that you want a list of.
Yes, tags and branches, too. But also the modules themselves. For
example, here is a list of all the modules for the viewcvs project:
http://cvs.sourceforge.net/viewcvs.py/viewcvs/viewcvs/
and here are those modules that are tagged as HEAD:
http://cvs.sourceforge.net/viewcvs.py/viewcvs/viewcvs/?
only_with_tag=HEAD
I imagine I could dig into the viewcvs code and find out how it
queries the CVS server. But that'd be a PITA for something that
should be pretty obvious. Actually, that might be an interesting
learning experience: using Eclipse to deconstruct the viewcvs code.
Regards,
- Robert
http://www.cwelug.org/downloads
Help others get OpenSource software. Distribute FLOSS
for Windows, Linux, *BSD, and MacOS X with BitTorrent
_______________________________________________
CWE-LUG mailing list
[email protected]
http://www.cwelug.org/
http://www.cwelug.org/archives/
http://www.cwelug.org/mailinglist/
--
Ed Howland
WDT Solutions, LLC.
[EMAIL PROTECTED]
(314) 962-0766
_______________________________________________
CWE-LUG mailing list
[email protected]
http://www.cwelug.org/
http://www.cwelug.org/archives/
http://www.cwelug.org/mailinglist/
