From: John Maher <JohnM_at_rotair.com>
Date: Thu, 22 Aug 2013 17:52:17 +0000
I'll try to clarify, everyone has their own copy of the tool. They also have their own copy of their settings. The problem arises because the tool stores the settings files in the same folder as some code specific files. This can not be changed. So within a single directory we need to version some files and ignore others.
Sure I could write a pre-processing program to do a multitude of things. It wouldn't be that hard. But then my plate has plenty of things that are not that hard. What will I gain? A happy working copy with a single command as long as what I write always works perfectly. Highly unlikely, so then I will make more problems for myself. Plus I assigned myself the task of learning subversion. Covering up a symptom does not treat the disease.
On Thu, Aug 22, 2013 at 12:15 PM, John Maher <JohnM_at_rotair.com> wrote:
So put them somewhere else or version them - and if the tool can't deal with multiple users, work out a way to script a rename the
Of course if it is too much trouble to clean up the files correctly, you can just delete the whole workspace and check out again to go between the branch/trunk versions.
> "Svn can't decide which of your files that it can't recreate for you should disappear."
How many people actually know which files subversion is ignoring?
-- Les Mikesell lesmikesell_at_gmail.comReceived on 2013-08-22 19:54:15 CEST
This is an archived mail posted to the Subversion Users mailing list.