Re: Making a copy that follows?

Blair Zajac wrote:

>
> That's actually a safety feature. Most of the time you don't want any
> outstanding changes in the externals committed just because you commit
> at the containing working copy. If the external exists because you want
> to share a piece of code with multiple projects, you do also want
> separate commits for the external and the code that uses the external.

That's absolutely okay and it is the way it should be.

But that's one more reason why svn:externals is not the solution to the
class of problem I am dealing with. It just is a solution to a very
different problem.

I'd still would prefer a way of simply having one repository file
appearing at several locations.

Something like

svn link pathA/fileA pathB/fileB

and then having both plain files with the same content.

If I understand subversion correctly, then this should be possible
without to many changes.

The only problem I see is when fileA and fileB are changed differently
within the same revision. This could require to simply commit them
separately, e.g. fileA as revision n and then an update for fileB, then
commit at n+1.

regards
Hadmut

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 31 00:00:40 2006