Re: Behavior of update command

On 2/28/06, Mark Phippard <markp@softlanding.com> wrote:
> > Ah, I see, the value of N is the same in both updates because the
> definition of
> > it is only the highest such number that was cached locally in the earlier
> step
> > (when "Synchronize" was chosen and a "status -u" was performed), and this
> cache
> > hasn't been updated to account for the commits that were performed in the
> mean
> > time.
>
> Yes, that is it exactly.
>
> > You're back to the problem of specifying exactly what you want
> conceptually.
>
> 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.

To me this would be a major break with current behavior (and with
expected behavior as even CVS does not do that)

Now, maybe there could be a useful option that has that type of behavior,
where it brings a file up to that revision if that revision is newer than
the current one but not if the file is newer than that revision.

However, changing svn up to do that with the -r option would break
things rather significantly. (I always assumed that if I did svn up -r N-1
that all files would then be at the N-1 revision - since that is what it does
and what CVS effectively does when done on a file's revision.)

--
Michael Sinz               Technology and Engineering Director/Consultant
"Starting Startups"                          mailto:Michael.Sinz@sinz.org
My place on the web                      http://www.sinz.org/Michael.Sinz
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org