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

Re: why does subversion make me update, only to get no changes?

From: Andy Levy <andy.levy_at_gmail.com>
Date: Wed, 28 Jan 2009 12:27:07 -0500

On Sat, Dec 27, 2008 at 19:02, Richard <legalize_at_xmission.com> wrote:
> Sometimes when I try to commit, subversion tells me that I have to update
> first. When I do the update, nothing changes in my local filesystem (no
> modified or added files appear), and then the commit succeeds.
> Why?

Because the repository revision has incremented, and your WC may not
be in sync with the repository anymore.

> This happens so often, that the subversion client should just
> automatically do the update when the first commit fails and then only
> fail to the user when a commit after the update also fails.

"Automatic" would result in people yelling that Subversion isn't doing
what they expect, or that they're losing local changes or something
else along those lines. Subversion assuming that you always want this
to happen may be an invalid assumption.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-28 18:30:41 CET

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.