Re: [Savannah-users] CVS - bad repository state / migration to git
Nicolas Neuss wrote: > Bob Proulx writes: > > After you are satisfied with the git repository if you let us know we > > can disable commits to the CVS repository. If someone tries to commit > > to it they will get a message that the repository is disabled instead > > of being confused by having it work. > > I think this would be the right moment for disabling CVS. Done! Any attempted commits there will get an information message. Bob
Re: [Savannah-users] CVS - bad repository state / migration to git
Bob Proulx writes: > Nicolas Neuss wrote: >> Hmm, I suspected that it might have something to do with that. So I >> guess that I will have to recommit those changes... > > For those latest changes, since you are planning on migrating to git, > the easiest thing would be to do the migration first and then add > those changes to the git side of things. Since git supports surgery > on the repository better than CVS does. So I would do the conversion > to git first and the addition of the missing history second. > > After converting to git then enable the git repository from the > Savannah web interface. Then push. Since the git repository is > initialized empty you can push your repository to it. After that it > has content and history and will be published.. > > Often there are false starts at the conversion. If you have just > recently converted to a fresh git repository but haven't gotten it > right the first time and need to do a second conversion please just > let us know that this is the problem and I can reset things for you so > that you can push again with your adjustments. That happens and we > understand the problem. It is good to get things finalized so that > things can move forward. After the conversion is complete and done > then you should consider that the published source is published. > Usually once published it can't be unpublished. All this worked very well. Many thanks to you and Andreas (and also to my colleague Stephan Weller here in Erlangen who helped me with git). > After you are satisfied with the git repository if you let us know we > can disable commits to the CVS repository. If someone tries to commit > to it they will get a message that the repository is disabled instead > of being confused by having it work. I think this would be the right moment for disabling CVS. Thank you, Nicolas
Re: [Savannah-users] CVS - bad repository state / migration to git
Nicolas Neuss wrote: > Hmm, I suspected that it might have something to do with that. So I > guess that I will have to recommit those changes... For those latest changes, since you are planning on migrating to git, the easiest thing would be to do the migration first and then add those changes to the git side of things. Since git supports surgery on the repository better than CVS does. So I would do the conversion to git first and the addition of the missing history second. After converting to git then enable the git repository from the Savannah web interface. Then push. Since the git repository is initialized empty you can push your repository to it. After that it has content and history and will be published.. Often there are false starts at the conversion. If you have just recently converted to a fresh git repository but haven't gotten it right the first time and need to do a second conversion please just let us know that this is the problem and I can reset things for you so that you can push again with your adjustments. That happens and we understand the problem. It is good to get things finalized so that things can move forward. After the conversion is complete and done then you should consider that the published source is published. Usually once published it can't be unpublished. After you are satisfied with the git repository if you let us know we can disable commits to the CVS repository. If someone tries to commit to it they will get a message that the repository is disabled instead of being confused by having it work. Bob
Re: [Savannah-users] CVS - bad repository state / migration to git
Nicolas Neuss writes: > But then I need to get the CVS repository which is on the Savannah > server to which I do not have direct access. Is there a way to extract > it? $ rsync rsync://cvs.sv.gnu.org/sources/ Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
Re: [Savannah-users] CVS - bad repository state / migration to git
Andreas Schwab writes: > Nicolas Neuss writes: > >> 1. I wanted to update the project from my local version which strangely >>did not work perfectly. It looks as if my local version contains >>-for some files- newer CVS version than are in the repository on >>Savannah. Did something happen in the recent years with Savannah >>such that an older repository state had to be restored? Or is there >>some other way in which something like that can happen? > > http://savannah.gnu.org/maintenance/Compromise2010/ Hmm, I suspected that it might have something to do with that. So I guess that I will have to recommit those changes... >> 2. What is the best way for migrating a Savannah project from CVS to >>git? > > I'd start with cvs2git. But then I need to get the CVS repository which is on the Savannah server to which I do not have direct access. Is there a way to extract it? > Andreas. Thank you, Nicolas
Re: [Savannah-users] CVS - bad repository state / migration to git
Nicolas Neuss writes: > 1. I wanted to update the project from my local version which strangely >did not work perfectly. It looks as if my local version contains >-for some files- newer CVS version than are in the repository on >Savannah. Did something happen in the recent years with Savannah >such that an older repository state had to be restored? Or is there >some other way in which something like that can happen? http://savannah.gnu.org/maintenance/Compromise2010/ > 2. What is the best way for migrating a Savannah project from CVS to >git? I'd start with cvs2git. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
[Savannah-users] CVS - bad repository state / migration to git
Hello, I have a CVS project (Femlisp) on savannah.nongnu.org which was inactive for about four years (at least the repository). Now I'm thinking about migrating to git and have some questions: 1. I wanted to update the project from my local version which strangely did not work perfectly. It looks as if my local version contains -for some files- newer CVS version than are in the repository on Savannah. Did something happen in the recent years with Savannah such that an older repository state had to be restored? Or is there some other way in which something like that can happen? 2. What is the best way for migrating a Savannah project from CVS to git? Thank you very much, Nicolas
