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

Re: subversion link capability

From: Joshua Varner <jlvarner_at_gmail.com>
Date: 2005-09-08 16:29:21 CEST

On 9/8/05, Grégoire Welraeds <gregoire.welraeds@side-international.com> wrote:
> In a project, he has file y in directory a which is a copy of file x in
> directory b. These files must be identical to each other when commiting
> changes to the repository otherwise it could break the application or at
> least produce some unexpected side effects. In SourceSafe, this was an easy
> situation as it seems that one can tell SourceSafe that file y is a link to
> file x and when checking one of the file, the other is automatically updated
> (I know almost nothing about SourceSafe). Since the project was migrated to
> svn, he now have to __manually__ copy the file before performing the commit.
> There is no need to think a long time to understand that this situation is
> prone to errors.
> At first, I told the developper that this was a bad idea to have the same
> file copied from to directories in the same project and that having a single
> file in a shared place would be a better design (in this case, the file is a
> header file).

Agreed, but some things are out of our control.

> Any clue?

Subversion supports symlinks, so you could change one half of each
pair to a symlink.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 8 16:31:36 2005

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

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