Jean-Marc van Leerdam wrote:
> As it is your tool can be useful, but (as you say in the readme) there
> is the possibility to lose data. And I think there are some major
> risks here, let me try to explain.
> As soon as you forget to copy from A to B before you start working on
> B (or vise versa) stuck with modifications in both places. As soon as
> you copy again, the changes you made in the target WC are gone.
> So it only takes one lapse of attention (running off to home friday
> afternoon without grabbing the latest WC from home or getting into
> office on monday morning realising the laptop with 48 hours of weekend
> work is still at home...) to get stuck or run the risk to lose amounts
> of work.
> And as an aside: messing with the .svn folders is not something that
> is encouraged to say the least.
> Don't get me wrong, I'm in favour of flexible working methods, but SVN
> (and consequently TSVN) are all about minimising the risk to lose data
> and at the moment your tool doesn't seem to honour that.
I designed the tool for _me_ (what do you expect from 150 lines of C++
code?). I'm merely sharing it because some people might want and
appreciate the flexibility even though there are risks. To use the tool
means they understand the risks of using the tool as well as
comprehending how advanced the tool is. I also made the tool to
demonstrate proof-of-concept that the feature idea I had is doable in
the first place.
As to the .svn folders themselves - there isn't much in there to mess up
in the first place. Only if the SVN developers start getting fancy is
there any real danger.
As to forgetfulness - I added another 170 lines of code to account for
your two examples, which, BTW, are the same issue.
Check out the updated SVNCopy (and documentation). I believe this new
version addresses your major concerns. If you like it and want to see
it put in TSVN and ask REAL nice, I might give the TSVN community the
source code to SVNCopy.
Safe C++ Design Principles (First Edition)
Learn how to write memory leak-free, secure,
portable, and user-friendly software.
Learn more and view a sample chapter:
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu Jul 20 00:13:46 2006