The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: SUBVERSION
by somekool on Sunday 24/Oct/2004, @21:42
|
right, I guess we would need to handle that case to.
well, before we write, I guess CVS is able to know if there was a file before or not.
in case where a new file is written over an old delete one, cvs could kinda "reopen" the file, and commit a new version to it. (even if completely different).
so the old exist and the new one too. the only big question, is how to make the file unexistent between the too alive state.
and I agree there... moving back the file is quite more interresting challenge, cuz we want to prevent all history right.
If we are moving the exact same file, we could run a diff. see, if <oldfile> goes from 1.1 to 1.24 and <new file> is 1.1 to 1.98 and all version from <oldfile> exist in new file, well, we can just copy over the new one to the old emplacement, cvs delete the old emplacement of the <new file> and we are pretty much ok to go. except if there is branches, I suppose it gets really really more complicated. but at least we got a hint for a way to go now. there is people out there much better than me which would think about what I don't.
this is feasable.
about the last case where you move an existing cvs file over a old cvs file location... this one becomes really tricky. since both history can hardly be kept. but I suppose this could be forbidden, or cvs could ask what do you want to do, like different scenario is possible.
come on guys.
|
[
Reply To This | View ]
|
Re: SUBVERSION
by JohnFlux on Tuesday 26/Oct/2004, @11:45
|
Hey good idea. Lets fix all the cvs bugs, but keep all the commands similar so as to not confuse anyone, and keep it basically the same.
Then we'll change the name of it from cvs to something else so as not to confuse anyone. svn sounds like a good name to change it to. Yeah lets do that!
Oh wait.
|
[
Reply To This | View ]
|
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
|