Re: [Jsynthlib-devel] XioSynth patch editor, 2nd try

[Joe E. <jo...@em...>]

Rib Rdb wrote:
> I'd recommend migrating to svn so we could use 
> http://codereview.appspot.com
One advantage of SVN is that it supports *moving* of files to different 
directories.

Long ago, in a galaxy far away, we had talked about refactoring all of 
the core JSL code into a more-sensible package structure. The downside 
to this was going to be that, when we moved the files, CVS would treat 
this like the file getting deleted from its old location and a 
completely new file being created at some new location. So, there's a 
break in the "lineage".

Granted, I'm sure it's easy to just roll back to a previous tag point... 
but it would just make it harder to view the history of revisions to the 
file.

Now, this is kind of a moot point because, back then, I did a /lot/ of 
work on refactoring. I moved a lot of the files around, heavily rebuilt 
the way GUI events are delivered to the synth editors, overhauled the 
MIDI interface. Now, I never committed it, because it still had a couple 
of compile bugs that I wasn't sure how to fix.

But the point is: all of those changes were done with Jetbrains IDEA 
when it understood the source management to be through CVS, not SVN. So, 
I'm sure it hasn't bothered to remember that all of these files have 
moved. So, if we switch to SVN, and then I commit all of this stuff, 
then SVN (like CVS) will probably just see it as a bunch of file 
deletions and then new file creations.

- Joe