Marc Haisenko wrote:
> On Tuesday 14 March 2006 09:47, Jean-Paul Hamerton wrote:
>> I have 2 CPP files that are the same in the SVN project but different
>> directories. When I update one I have to always have to update the
>> other.
>>
>> I would like not to have to do this last step as some times I forget.
>> I was thinking to move all this stuff to a "common" directory.
>> But I thought maybe SVN can do this for me just have 2 files that are
>> linked together if you update one the other is always updated.
>>
>> any help?
>>
>> thx
>
> No SubVersion can't do this... some version control systems a capable
> of such things but I personally think this is potentially dangerous:
>
> Imagine you could link them together so that changes in one file
> appear in the other. Your file is now existing in two different
> contexts. Imagine, one year from now, you have forgotten that they
> are linked and change it in one context and a few days later some
> developer working on the second context is wondering why his
> application is crashing all the time... even worse is when it's the
> customer experiencing problems because of this.
Don't remind me: I went through this with a symlink change in Perforce,
which proceeded to allegedly accept the symlink change in the repository,
but didn't actually change the link. When I checked it out, it pointed to
the old location and I proceeded to mess up a critical configuration file
that I thought pointed to a development location.
This was..... a problem.
Fortunately for me, subversion seems to handle symlinks much, much better.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 14 14:17:08 2006