Vinh Pham wrote:
>
> That's a good idea. Unfortunately, that means we have to get into the
> whole cvs watch on/off, cvs edit things. For me, it maybe OK but most of
> my co-workers are not software-oriented. Adding that level of complexity
> may not work well for them. I've been advising people to use the command
> cvs status | grep Need.
> However, this doesn't work with newly added file. Do you have any other
> ideas? I wonder whether adding an additional flag to the status command
> would be a good feature to add (if nothing equivalent existed yet.)
>
This is not exactly intuitive, but the best way I've found
is
cvs -nq update
which lists what would happen if cvs did do an update. The -n
means "Don't do anything!" and is useful if you are just looking
for the output of a command, and -q suppresses some lines I
don't find useful.
It will list files, one line per file. If the file begins with
a ?, cvs knows nothing about it (and it isn't in .cvsignore).
If it begins with U, somebody's added it. If it begins with a
P, somebody's changed it. If it begins with an M, you changed
it; if somebody has checked in a change, you'll get a message
about the changes being merged. If it begins with a C, then
your version is incompatible for some reason with the version
in the repository, usually because both you and somebody else
have made conflicting changes.
--
David H. Thornley Software Engineer
at CES International, Inc.: [EMAIL PROTECTED] or (763)-694-2556
at home: (612)-623-0552 or [EMAIL PROTECTED] or
http://www.visi.com/~thornley/david/
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
