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

Re: svn update -N breaks working copy? (At least a little bit)

From: Roland Schwingel <Roland.Schwingel_at_onevision.de>
Date: 2003-11-05 16:41:35 CET


Ben Collins-Sussman <sussman@collab.net> wrote on 05.11.2003 16:27:54:

> On Wed, 2003-11-05 at 09:00, Roland Schwingel wrote:
> > A bug? I am using subversion 0.32.1. It appears that it is triggered by
> > 2 times 'svn update -N'
> This is crazy. We need to get rid of the -N flag for 'svn up' before
> svn-1.0. It's way too confusing, and barely works at all. I'd rather
> nuke it, and then implement a true --depth= argument in svn 1.1.
Well. I like the feature to not recursive update certain folders!
(The case above is just constructed to reproduce the problem, not the real
 world way to use it).Often I do have a larger trees, and from commit mails
I know what has changed so updating just the current folder is much nicer,
than updating the whole tree because it is much faster...


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 5 16:42:39 2003

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.