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

Re: My Backup Script

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: Tue, 26 Jul 2011 13:55:17 -0500

On 7/26/2011 1:47 PM, Andreas Krey wrote:
>>> This is one of the high strangitude svn behaviour artefacts: That you
>>> can't do two consecutive commits without getting an error (in some
>>> relatively popular cases).
>> And you generally shouldn't be doing that unless there is some special
>> need to avoid picking up concurrent changes
> No, there are no concurrent changes. I'm the only one working the repo;
> For the second of the back-to-back commits I got the error, which is
> easily explained when you know about mixed revisions and that. But at the
> same time it looks utterly idiotic, since the WC was up to date before,
> so how can it possibly be not up to date after the first commit.

How could it possibly be up to date if there has been a commit since the
last time it was updated?

   Les Mikesell
Received on 2011-07-26 20:55:57 CEST

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.