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

Re: Behavior of update command

From: Julian Foad <julianfoad_at_btopenworld.com>
Date: 2006-03-01 15:52:48 CET

Michael Sinz wrote:
> On 2/28/06, Mark Phippard <markp@softlanding.com> wrote:
>>
>>I do not know if I want anything, I mainly just need to write it out for my
>>own benefit although the discussion has been helpful. If I did want
>>something, then I would want a way for:
>>
>>svn up -r N
>>
>>to not update any files or folders that are > N, just the ones that are < N.
>
[...]
> Now, maybe there could be a useful option that has that type of behavior,
[...]
> However, changing svn up to do that with the -r option would break
> things rather significantly. [...]

Michael, don't worry - Mark's not asking to change any default behaviour. I
don't think he even wants this extra feature exposed in "svn"'s UI, only as an API.

Mark, in my opinion, I'm not convinced that this feature is justified by your
use case for it, but if you want to pursue it further you could send a more
formal proposal in a new thread and see what others think. You maybe ought to
pursue other directions, such as performing an update on only the list of files
that you want to update. If the API for doing this is too slow, it ought to be
speeded up.

- Julian

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 1 15:57:25 2006

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

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