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

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.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1063726

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