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

Working with renamed files

From: Greg Ward <gward_at_mems-exchange.org>
Date: 2003-01-16 23:22:50 CET

I don't know if this is a bug or a mismatch between my mental model and
Subversion. But it sure is annoying: I am unable to do much with files
that have been renamed or moved. Bug #1094 reports my first encounter
with this; here's my second.

In rev 20215 and 20216 of our repository, a bunch of stuff was moved
around, so what used to be

is now

(svn is our local Subversion server; the repository root is
http://svn/repos/ .)

For various reasons, I wanted to step back in time and look at how
things were before the big move, so I did this:

  svn co -r20214 http://svn/repos/trunk/vfab

As expected, I can now find vfab/CHANGES.txt in my working copy. If I
did a straight "co" with no "-r", I would expect to see
vfab/lib/CHANGES.txt instead.

But I can't actually *do* anything with it, apparently because of the

  $ svn log CHANGES.txt
  svn: Filesystem has no item
  svn: REPORT request failed on /repos/trunk/vfab
  file not found: revision `20233', path `/trunk/vfab/CHANGES.txt'

If I do "svn log lib/CHANGES.txt", I get the complete log.

But that means that, at some level, Subversion is ignoring the fact that
my "co -r 20214" stepped back in time a day. Never mind the *current*
state of the tree: I explicitly asked to see the state of the tree as of
rev 20214. But something is preventing me from seeing the full tree:
sure I get the contents and location of CHANGES.txt as of rev 20214, but
what about its revision history?

Is this a shallow little bug? A deep design problem? Or am I just
failing to appreciate Subversion's view of the world?


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jan 16 23:23:35 2003

This is an archived mail posted to the Subversion Dev mailing list.

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