[openbeos] Re: It is accomplished -- no version history
- From: "Daniel Reinhold" <danielr@xxxxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Tue, 09 Jul 2002 14:55:17 CDT
>"Daniel Reinhold" <danielr@xxxxxxxxxxxxx> wrote:
>>Another item about the new CVS files:
>>
>>Would it not have been possible to import the files to their new
>>locations, rather than just checkin? There is no version history in
the
>>new structure. All files are now v1.1, author 'ejakowatz', with
>>comments "It is accomplished...". This is unfortunate.
>
>If you don't like the comment, you can change it with the cvs admin
feature.
Oh please! As if I give a poop what the current comment is. My point is
that all of the original authors/submitters comments are gone. And all
the diffs. They track what has happened with the file over time. This
is *particularly* useful with the kernel -- it lets us know what we
have done since the fork from NewOS.
Ok, I just tried a test import (at /shtest) and, sure enough, all the
revision history is gone. Well, this really sucks.
If we can save the revision history with help from the SF tech support,
we should do this. If we can't -- well, then I guess that is that.
However, we should at least archive the current repos and save it as a
resource, in case we need to go look something up, Heck, I'll probably
save a copy locally myself, just to be sure we have at least one.
>Regarding the loss of history:
>Yes, this is unfortunate. I don't like it either. But it's not that a
big problem I think.
>We should move forward, and don't look back. It would have been
possible to
>keep the history with help from SF, and some more work. But there
unfortunately
>is no cvs command to move a file.
>
>http://cvsbook.red-bean.com/cvsbook.html
>
>| I need to move files around without losing revision history
>| In the repository, copy (don't move) the RCS files to the desired
new location in the project.
>| They must remain in their old locations as well. Then, in a working
copy, do:
>| floss$ rm oldfile1 oldfile2 ...
>| floss$ cvs remove oldfile1 oldfile2 ...
>| floss$ cvs commit -m ?Òremoved from here?Ó oldfile1 oldfile2 ...
>| When people do updates after that, CVS correctly removes the old
files and brings the new
>| files into the working copies just as though they had been added to
the repository in the
>| usual way (except that they'll be at unusually high revision numbers
for supposedly new files)
>
>regards
>Marcus
>
Other related posts:
