[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: why subversion?

From: Pierrick LE GALL <plegall_at_talend.com>
Date: 2006-10-06 09:22:38 CEST

"Bruce Thompson" <bruce@otherother.com> writes:

> In CVS it is not possible to check the status of a file without
> updating that file [...]

Why not running "cvs update" in dry-run mode? With this workaround you
can see if a file has a new version on the current branch or if you have
a local modification.

$ cvs -nq up
M file1 # localy modified
G file2 # localy modified + new version on repository + successful merge
C file3 # localy modified + new version on repository + conflicting merge
U file4 # new version on repository
A file5 # file to be added in next commit
? file6 # unversionned file

That's not pretty as "svn status --show-updates" can be, but it's very
useful when you can't migrate to Subversion :-)

-- 
Pierrick LE GALL
R&D engineer at Talend, Open data solution
http://www.talend.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 6 09:23:04 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.