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

RE: Managing duplicate and near duplicate files

From: Giulio Troccoli <Giulio.Troccoli_at_uk.linedata.com>
Date: Fri, 9 May 2008 12:29:31 +0100

After a file or directory is copied there will be no relation between
the two, i.e. a change in the original one will not be automatically
made into the copy. You will have to merge the changes manually.


So to answer your question the only way I know is to set up a script
that does that for you. But remember, the merge operation needs a
working copy (it cannot be done directly on the repository like the copy
for example) and you will have to commit the changes after the merge.


For duplicates (not near duplicates) there could be a solution, but all
the original files must be in the same directory. If that is true you
can use the svn:external property to basically create a link between the
original directory and the directory where the property is set. When the
destination directory is checked-out or updated, the "linked" directory
is checked-out or updated to. This means that any change in any of the
files in the original directory will be brought into the new directory
too. And you can add the svn:external property to as many directory as
you want.





From: Richard Yale [mailto:Richard.Yale_at_uk.linedata.com]
Sent: 08 May 2008 16:23
To: users_at_subversion.tigris.org
Subject: Managing duplicate and near duplicate files


Hi I'm quite new to subversion so sorry for bad terminology, or a silly
question. I couldn't find my answer in the archive.

We've recently moved a file set over to subversion to manage changes to
and growth of this set. The set includes many duplicate and near
duplicate files (often with different names) across many directories
which I've identified and created SVN scripts to delete (near)duplicates
and SVN copy them back then restore the true file so that subversion
will know they were born from one original file and that they were

A change to one of these files usually needs to go into each of them so
my question is this: Is there a manageable way for me and other
contributors to change one of these files then roll out the change
across each duplicate and near duplicate file, if needed, without
needing to know which other files should take the change? I guess I
could write a script that will merge a change to a list of a file's
relations but that would be a lot of work to make reliable and would
need manual updating when a new duplicate file was made.

The file names and locations can't be changed for legacy reasons but I
could create a new directory with a "master" copy of these files if that
gets a simpler solution. The files are used from windows machines by the
way so I think that rules out any kind of symbolic link solution for the
exact duplicates.






Linedata Services (UK) Ltd
Registered Office: Bishopsgate Court, 4-12 Norton Folgate, London, E1
Registered in England and Wales No 3027851 VAT Reg No 778499447


Received on 2008-05-09 13:29:11 CEST

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.