Subversion error when building submodule from tag

[GoogleCodeExporter]

Suppose a repository with this layout:

http://localhost/svn/
  trunk
    module-a
  tags

If a user copies trunk to tags/1.0, the path tags/1.0/module-a would now
exist, but the Last Changed Rev for the new path tags/1.0/module-a would be
the same old revision as trunk/module-a, whereas tags/1.0 would not exist
yet in that old revision.

This causes a "not found" error because the Subversion plugin tries to
create a working copy from a revision where the new tagged path does not
exist yet.

Original issue reported on code.google.com by chris.eldredge@gmail.com on 4 Apr 2007 at 5:48

[GoogleCodeExporter]

Fixed in r370 by getting the revision of the most recent log entry on the 
relative
path.  This revision is sometimes different from the Last Changed Revision for 
the
same path, and is more correct.  The only downside is it will take 2 round 
trips to
the server in getLatestRevision instead of one.

Original comment by chris.eldredge@gmail.com on 4 Apr 2007 at 7:20

• Changed state: Fixed