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

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

From: Mark Phippard <markp_at_softlanding.com>
Date: 2005-10-06 15:13:56 CEST

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

> 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.

My guess is that the first svn up is not being done on the folder where
the prop-change is being made, so it is not updated to the HEAD revision.

When I try the same set of commands I do not have a problem. Of course
there is no "svn ignore" command, so for that step I am setting the
svn:ignore property on a folder that I previously updated.

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Thu Oct 6 23:13:56 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.