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

AW: Re: AW: Re: AW: Re: Commit Failed

From: Markus Karg <markus.karg_at_quipsy.de>
Date: 2005-10-06 15:06:59 CEST

I want to ask them why I have to do that:
 
svn up
svn ignore
svn up
svn ci
 
(works well)
 
while I actually want to do that:
 
svn up
svn ignore
svn ci
 
(tells me outdated transaction)
 
The question is: If there is no other person working on that repository, and those commands are run in that direct sequence (in a batch, done in less than a second), why is svn ci complaining of outdated transactions? The reasons told in the FAQ are not matching my situation here.
 
That's what I want to ask them.
 
 
 
Mit freundlichem Gruss / With kind regards
Markus KARG, Staatl. gepr. Inf.
Entwicklung / R & D
QUIPSY QUALITY GmbH

________________________________

Von: Mark Phippard [mailto:markp@softlanding.com]
Gesendet: Do 06.10.2005 15:05
An: users@subclipse.tigris.org
Betreff: Re: AW: Re: AW: Re: Commit Failed

"Markus Karg" <markus.karg@quipsy.de> wrote on 10/06/2005 09:03:24 AM:

> I checked a few things and I am convinced that it is not a Subclipse
problem:
> It also happens when I'm using svn command line. :-(
>
> So I'll ask again on the SVN mailing list.

What is there to ask? You need to run svn up on the folder.

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Thu Oct 6 23:06:59 2005

This is an archived mail posted to the Subclipse Users mailing list.

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