On Thu, Aug 22, 2013 at 12:15 PM, John Maher <JohnM_at_rotair.com> wrote:
> "How about just 'delete the spurious unversioned files yourself'?"
> As I said in the previous reply, two of those files are user settings. They would have to be constantly recreated by the developer. That increases costs. One of the reasons I wanted some form of source code control was to reduce costs.
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
correct copy for the current user. A clever developer should be able
to find an alternative to forcing subversion to keep a versioned
directory in conflicting place or retyping a file to recreate it when
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."
> It could ignore files that it is instructed to ignore. That would help.
How many people actually know which files subversion is ignoring?
Again, a clever developer could probably come up with his own way to
delete files matching some patterns if he really wants that to happen.
Received on 2013-08-22 19:30:50 CEST