On Thu, Aug 22, 2013 at 12:52 PM, John Maher <jo...@rotair.com> wrote:
> 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?
Things that don't mysteriously break? Reproducible builds? Are
those worth anything?
> 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.
If you want to rely on the contents of dirty workspaces, just check
out different copies for each branch and let the cruft live there as
long as you need it. You can still update/commit independently, etc.
But you need to understand that the cruft is yours, not subversion's
and whatever you are doing isn't reproducible.
--
Les Mikesell
lesmikes...@gmail.com
