"Gale, David" <David.Gale@Hypertherm.com> wrote on 01/31/2006 01:39:18 PM:
> I'd second this idea.
>
> Given:
>
> /foo
> - file1
> /bar
>
> svn link svn://example.com/foo/file1 svn://example.com/bar/file2
>
> Should produce:
> /foo
> - file1
> /bar
> - file2
>
> At which point, the following should be true:
> svn co svn://example.com/
> cd bar
> <change file2>
> svn ci
> cd ../foo
> svn stat -u
> U file1
>
>
> Any other design thoughts? Any votes against, or shall we pass this on
> to the dev list?
I wouldn't say that I am against it, but I think there are so many edge
cases to consider that you have little chance of ever seeing someone try
to implement it.
First off, let me just say that your example does a nice job of expressing
what you see as the requirements. But let's be realistic here. Once your
repository is materialized into a working copy you have to start dealing
with the realities and limitations of the local file system. In your
example, how do you see the working copy code being able to see file1 as
having been changed, when it hasn't been?
Now for a few quick edge cases:
What if file1 and file2 are both modified in the working copy?
What does svn delete of one of the files do? What if one is changed and
the other deleted?
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@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jan 31 19:59:42 2006