git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon 'corecode' Schubert <corecode@fs.ei.tum.de>
To: "Uwe Kleine-König" <ukleinek@informatik.uni-freiburg.de>,
	git@vger.kernel.org
Subject: Re: cvsimport/cvsps: wrong revisions in branch
Date: Thu, 25 Jan 2007 17:24:49 +0100	[thread overview]
Message-ID: <45B8D9D1.2000802@fs.ei.tum.de> (raw)
In-Reply-To: <20070125150536.GA8314@cepheus>

[-- Attachment #1: Type: text/plain, Size: 2115 bytes --]

Uwe Kleine-König wrote:
> I don't know ruby nor hg, but I managed to clone your repo.  Now I'm
> stuck with:
> 
> 	zeisberg@cepheus:~/hsrc/fromcvs$ ruby1.8 fromcvs.rb 
> 	fromcvs.rb:1:in `require': no such file to load -- rcsfile (LoadError)
> 	        from fromcvs.rb:1

yes, you need the rcsparse module, available from the same address.

> Is there some documentation how to get that to work?

I've written it a million times to different people on irc, but somehow I never got around to making a README out of it.  I'll write it up very condensed here and add this as a base for a README to the the repo.

From CVS to * in little time
============================

Prerequisites:
  - ruby (1.8.5 known working)
  - fromcvs, <http://ww2.fs.ei.tum.de/~corecode/hg/fromcvs>
  - rcsparse, <http://ww2.fs.ei.tum.de/~corecode/hg/rcsparse> (ruby module)
  - Ruby/RBTree, <http://raa.ruby-lang.org/project/ruby-rbtree/>
  - for git: git-fast-import, <git://repo.or.cz/git/fastimport.git/>
  - for hg: ruby-python, <http://ww2.fs.ei.tum.de/~corecode/hg/ruby-python>


How to convert a CVS repo:

There is still a nice frontend missing, so you have to invoke the scripts by hand.

% mkdir gitdest && (cd gitdest && git init)
% ruby togit.rb /path/to/cvsroot modulename gitdest
% cd gitdest && git-repack -a -f -d      # optional, saves 20% or so

If you want to get nice author names, create setup the file authormap:

cat > /path/to/cvsroot/CVSROOT/authormap
corecode	Simon 'corecode' Schubert <corecode@fs.ei.tum.de>
jdoe		Jon H. Doe <hannidoe@example.net>
branch-fixup	CVS repo conversion <flames@example.net>

that's about for the quickstart.  be sure to report conversion errors or runtime issues (possibly due to obscure CVS repo activity) to me.

cheers
  simon

-- 
Serve - BSD     +++  RENT this banner advert  +++    ASCII Ribbon   /"\
Work - Mac      +++  space for low €€€ NOW!1  +++      Campaign     \ /
Party Enjoy Relax   |   http://dragonflybsd.org      Against  HTML   \
Dude 2c 2 the max   !   http://golden-apple.biz       Mail + News   / \


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  reply	other threads:[~2007-01-25 16:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-25 14:22 cvsimport/cvsps: wrong revisions in branch Gerrit Pape
2007-01-25 14:35 ` Simon 'corecode' Schubert
2007-01-25 15:05   ` Uwe Kleine-König
2007-01-25 16:24     ` Simon 'corecode' Schubert [this message]
2007-01-25 17:52   ` Shawn O. Pearce
2007-01-26  2:06   ` Martin Langhoff
2007-01-26  6:20     ` Simon 'corecode' Schubert
2007-01-26 23:12       ` Robin Rosenberg
2007-01-26  9:00     ` Gerrit Pape
2007-01-26 11:56   ` Jakub Narebski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45B8D9D1.2000802@fs.ei.tum.de \
    --to=corecode@fs.ei.tum.de \
    --cc=git@vger.kernel.org \
    --cc=ukleinek@informatik.uni-freiburg.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).