option for cvs update -C

[Brandon Ehle <az...@yahoo.com>]

He is basically looking for the cvs option of "cvs update -C".  Svn 
revert does NOT work because you cannot do a "svn revert -r HEAD", which 
would probably work.

 From a member of my dev team:

Does Subversion have the feature, or plan to add the feature, to force 
'svn update' to overwrite obstructing files?  Currently it reports the 
first obstructed file it finds and exits, regardless if there any more 
obstructed files that follow it.  It would be nice if at least it listed 
all the obstructed files it finds before exiting.

The situation I ran into was a number of build generated files was added 
to the repository by someone.  Then I update, and having already built 
those files, had to update, remove the first offending file, update 
again, remove next offending file, repeat until update succeeds.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: option for cvs update -C

[Karl Fogel <kf...@newton.ch.collab.net>]

Brandon Ehle <az...@yahoo.com> writes:
> He is basically looking for the cvs option of "cvs update -C".  Svn
> revert does NOT work because you cannot do a "svn revert -r HEAD",
> which would probably work.
> 
>  From a member of my dev team:
> 
> Does Subversion have the feature, or plan to add the feature, to force
> 'svn update' to overwrite obstructing files?  Currently it reports the
> first obstructed file it finds and exits, regardless if there any more
> obstructed files that follow it.  It would be nice if at least it
> listed all the obstructed files it finds before exiting.
> 
> The situation I ran into was a number of build generated files was
> added to the repository by someone.  Then I update, and having already
> built those files, had to update, remove the first offending file,
> update again, remove next offending file, repeat until update succeeds.

Yeah, agree -- I think we've even noticed this misbehavior before and
looked into fixing it.  If there's no issue filed already, could you
file one?  Obstructions should at the very least be listable all at
once (although I don't know what implications that might have for
libsvn_wc); and also 'update --force' should D.T.R.T.

-K

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org