search for: cvs2svn

All, We are considering removing some branches and tags in the conversion process from CVS to SVN. We don't want to do this in a vaccuum, so please read carefully. A deficiency in the cvs2svn script causes it to bloat the Subversion repository (significantly, as in 10x) in the conversion of branches and tags. We can minimize the impact of this by only keeping branches and tags that we really need. This gives us an opportunity to clean up some "dead wood" too. Obviously, I don&...

Hi Reid, > A deficiency in the cvs2svn script causes it to bloat the Subversion > repository (significantly, as in 10x) in the conversion of branches > and tags. It's probably a bit late in the day, but have you considered other CVS to SVN conversion tools, e.g. Tailor? http://www.darcs.net/DarcsWiki/Tailor http://da...

I've been wondering if we should consider migrating from CVS to Subversion (aka SVN) for version control. There's a utility (cvs2svn) to convert a CVS repository while keeping full history. And SVN is supported by viewcvs (as used by http://cvs.xapian.org/) The main motivations are: * CVS doesn't really handle renaming files well. Either you "cvs rm" then "cvs add" and have to manually step between...

...UPS Tools repo.) First, repostreamer per se is dead. As it evolved it kept pulling in more bits of code from reposurgeon until I said "screw it!" and merged the repostreamer logic in as a reposurgeon input stage. The NUT repo has some *strange* quirks. They seem to be consequences of a cvs2svn lift in the past; this is...normal. All that stuff will get cleaned up and untangled by the time I'm done. I've dealt with the issue in interpreting mixed-copy commits that I mentioned in previous listmail. One of Subversion's odder features, the representation of tags and branching a...

On Mar 20, 2004, at 1:07 PM, Ralph Giles wrote: > Ok, I'm starting the conversion. Please hold all commits until > further notice good luck! let me know how the cvs2svn script works out for you... I'm looking at doing the same soon with a ~800 file cvs repository I'm in charge of. /dale --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'ice...

I've solved the detached-branch problem! It wasn't actually the branch-rename overwrites that were doing this - turns out I was trying to remove cvs2svn-generated junk commits too soon and in the process deleting critical branch links. I've uploaded a new tarball to http://www.catb.org/esr/nut-conversion/nut-conversion.tar.gz with the 2.0-pre3 version of reposurgeon in it. That leaves two remaining issues. 1. Exactly what *is* the right w...

...http://llvm.cs.uiuc.edu/ On Apr 2, 2007, at 1:08 PM, Reid Spencer wrote: > All, > > We are considering removing some branches and tags in the conversion > process from CVS to SVN. We don't want to do this in a vaccuum, so > please read carefully. > > A deficiency in the cvs2svn script causes it to bloat the Subversion > repository (significantly, as in 10x) in the conversion of branches > and > tags. We can minimize the impact of this by only keeping branches and > tags that we really need. This gives us an opportunity to clean up > some > "dead...

This is taking longer than I expected, because there is all kinds of cvs2svn-generated ugliness in your back history that tends to crash my tools. Your repo makes a great test case. (Yes, I know, that's like having someone say "Your dog is fantastically ugly!") Current state of things is that I have scrapped my precious approach, which was to put the Subvers...

...07, at 1:08 PM, Reid Spencer wrote: > > > All, > > > > We are considering removing some branches and tags in the conversion > > process from CVS to SVN. We don't want to do this in a vaccuum, so > > please read carefully. > > > > A deficiency in the cvs2svn script causes it to bloat the Subversion > > repository (significantly, as in 10x) in the conversion of branches > > and > > tags. We can minimize the impact of this by only keeping branches and > > tags that we really need. This gives us an opportunity to clean up >...

So the Github-Importer screws up the old dark places of the SVN-History and the scripts try to handle this? 2017-01-13 22:57 GMT+01:00 James Y Knight via llvm-dev < llvm-dev at lists.llvm.org>: > I've been working on some scripting for re-converting the svn repository > into git. > > The existing git conversions are entirely sufficient for day-to-day > development

...sh to receive Subversion commit notifications. Our ports, doc and www trees are not affected at this time. A separate decision will be made regarding the direction of those CVS repositories soon. Many people have contributed to the effort, but I particularly wish to thank Michael Haggerty and the cvs2svn project developers for their assistance with extracting and decrypting our 14 years of CVS history. Yahoo (my employer) donated server hardware and allowed me to spend a considerable amount of time on the preparation, assembling the infrastructure, and the conversion. -- Peter Wemm - peter@wemm....

I'm currently working out how best to use cvs2svn to convert the CVS repo. I'm wondering if we want to strip out some of the tags - in particular the old snapshot_* tags. These mark points when the code was know to bootstrap and pass "make distcheck" on x86 linux, but the newest is 2001/04/24 - back in the BrightStation days! In t...

...> We have exactly one: data/html/nut-banner.png > > hmm, appears broken in Trac, but I'll check when I get home to see if > it's a problem with Trac or the SVN import. It turns out that the copy of nut-banner.png in CVS was not tagged as a binary ('-kb' sticky tag), so cvs2svn tried to convert the line endings to the Unix \n style. I changed the tag, reimported the CVS repository, and everything looks OK now. -- - Charles Lepple

...y with the branch link deduction, but I think this is the best we're going to do without manual intervention to break some harmless but spurious parent links. The underlying problem is twofold: (1) The repo history is cluttered with odd little single-file copies, probably mostly generated by cvs2svn. These show up in gitk as merge bubbles with no commits on one side. The smallest such glitch looks like this in the commit graph: | o |\ | \ | o | / |/ o | (2) There...

http://dovecot.org/test/ Sorry for not answering any questions for past two weeks, I'll try to get around answering them in next few days. I've also been thinking about if I should switch from CVS to Darcs. It seems to be exactly the kind of reversion control tool I had wanted to use. Anyone have comments for or against it? I'd still have read-only CVS repository generated from

...'ve been wanting to do this for some years, but have been waiting for a conversion script that could deal with our creaky old cvs repository. Subversion, although perfectly usable for the past two years, recently announced a stable 1.0 release, and more importantly the major issues with the cvs2svn script seem to have been resolved. So, time to make the switch. Please hold commits this coming saturday, march 20 until the change over is made. Up to friday, commit to cvs as usual. I'll do a fresh conversion from cvs during the dead period and announce when commits can begin under svn....

...'ve been wanting to do this for some years, but have been waiting for a conversion script that could deal with our creaky old cvs repository. Subversion, although perfectly usable for the past two years, recently announced a stable 1.0 release, and more importantly the major issues with the cvs2svn script seem to have been resolved. So, time to make the switch. Please hold commits this coming saturday, march 20 until the change over is made. Up to friday, commit to cvs as usual. I'll do a fresh conversion from cvs during the dead period and announce when commits can begin under svn....

...'ve been wanting to do this for some years, but have been waiting for a conversion script that could deal with our creaky old cvs repository. Subversion, although perfectly usable for the past two years, recently announced a stable 1.0 release, and more importantly the major issues with the cvs2svn script seem to have been resolved. So, time to make the switch. Please hold commits this coming saturday, march 20 until the change over is made. Up to friday, commit to cvs as usual. I'll do a fresh conversion from cvs during the dead period and announce when commits can begin under svn....

...'ve been wanting to do this for some years, but have been waiting for a conversion script that could deal with our creaky old cvs repository. Subversion, although perfectly usable for the past two years, recently announced a stable 1.0 release, and more importantly the major issues with the cvs2svn script seem to have been resolved. So, time to make the switch. Please hold commits this coming saturday, march 20 until the change over is made. Up to friday, commit to cvs as usual. I'll do a fresh conversion from cvs during the dead period and announce when commits can begin under svn....

Rafael, On Mon, 2006-11-27 at 16:05 -0300, Rafael Espíndola wrote: > Just wondering: Is there any plan to move to svn? I would love to have > a diff command that works when I am offline :-) Its been discussed from time to time. I would like to see this as well, but for an additional reasons: simpler branch management and faster updates, etc. SVN handles directories better and merging head