Robert P. J. Day [mailto:[EMAIL PROTECTED] wrote: > this resembles something i (as a newbie) have been thinking > about recently > -- what are all the ways i can just *query* with regards to a CVS > repository? it's this querying that seems to get such short > shrift in the > CVS documentation i've seen. [...]
> so all the different ways to query an existing repository > would be a good > start. Hmm... I've been doing it for so long, I don't even think about the different ways to do it. How about we start this way - you ask specific questions about what you want to know, and keep track of the answers you get. Once you've built up a few, submit a patch for the documentation. One I find very useful, and which I _think_ is documented, is: cvs -nq up This gives you a list of files that need to be checked in, updated, and "unknown" files - the ones that you may have forgotten to check in. -- Jim Hyslop Senior Software Designer Leitch Technology International Inc. (http://www.leitch.com) Columnist, C/C++ Users Journal (http://www.cuj.com/experts) _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
