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

Re: trying to get new version of files from svn archive

From: <dov.kruger_at_americas.bnpparibas.com>
Date: Mon, 25 Apr 2011 11:08:49 -0400

Take it as fact that I'm not interested in my version of the file. So
anything svn may have decided about resolving collisions is irrelevant.

I want to get rid of my version of the file and get the one in the
archive. I think the reason for my confusion was that the file itself no
longer exists.

However, to clarify for everyone, we are using svn 1.6.15, which is pretty
recent under linux.

my SVN_EDITOR is emacs.

Internet
subversion-2011a_at_ryandesign.com
04/25/2011 10:43 AM

To
Dov KRUGER
cc
users_at_subversion.apache.org
Subject
Re: trying to get new version of files from svn archive

On Apr 25, 2011, at 09:34, dov.kruger_at_americas.bnpparibas.com wrote:

> Excuse my ignorance, I'm used to cvs.

I have never used cvs, so my advice may not exactly correspond.

> I edited some files at the same time as a colleague, but when we
realized, he went forward, so my copies were obsolete.

Not necessarily. You might have made changes to different parts of the
file, which subversion would have resolved for you, in a probably proper
manner.

> Some time later, I tried to update, to get the new files, and to get his
updated version.
>
> It reported the files changed, just as I would see in cvs:
>
> C A.txt

Ok, a conflict occurred, so you and he did modify similar-enough parts of
the file that subversion could not automatically merge them. You would now
usually resolve the conflict manually.

http://svnbook.red-bean.com/en/1.5/svn.tour.cycle.html#svn.tour.cycle.resolve

You usually do this by opening the file in an editor and picking the
correct lines from amongst those subversion has indicated in the file for
you. You can also make use of the three additional files subversion has
created (one containing the old file, one containing the new upstream
file, and one containing your version) to assist you in deciding what's
right.

> Since I wanted the new ones, I first looked for the equivalent of
>
> cvs up -C
>
> thinking it was:
>
> svn up --force
>
> but it wasn't.
>
> So then I deleted the files (so I don't have a local copy at all) and
again:

Ok, now you don't have the file at all.

> svn up
>
> Subversion just reports the current version number and does not try to
bring the files in as cvs would.

This should indeed have brought back the current version of the file. Are
you sure it did not?

This message and any attachments (the "message") is intended solely for
the addressees and is confidential. If you receive this message in error,
please delete it and immediately notify the sender. Any use not in accord
with its purpose, any dissemination or disclosure, either whole or partial,
is prohibited except formal approval. The internet can not guarantee the
integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will)
not therefore be liable for the message if modified. Please note that certain
functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.
Received on 2011-04-25 17:09:20 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.