threads / discuss / 428

Anyone working on a CVS->git converter?

Subject: Anyone working on a CVS->git converter?

## tl;dr

3 messages between May 2, 2005 and May 3, 2005.

replies: 2people: 3as markdown or json

Juliusz Chroboczek· May 2, 2005, 16:11 UTC · re: H. Peter Anvin · lore

Re: Anyone working on a CVS->git converter?

> Anyone working on a CVS->git converter?
Not directly, but you might get your wish Real Soon Now.

I'm currently putting the finishing touches on commit support for darcs-git. Once that's finished, you should be able to run tailor (the CVS to Darcs converter) over a Git repository.

So hold on for a few days, and drop me a mail if you don't hear from me.

                                        Juliusz
Kay Sievers· May 3, 2005, 00:28 UTC · re: H. Peter Anvin · lore

Re: Anyone working on a CVS->git converter?

On Sun, 2005-05-01 at 18:42 -0700, H. Peter Anvin wrote:
> Anyone working on a CVS->git converter?  I'd like to move klibc 
> development into git.
I tried it with two completely stupid scripts and the nice cvsps.
Here is the tree to browse:
  http://ehlo.org/~kay/git/gitweb.cgi?p=klibc.git;a=log
In the CVS repo directory export patchsets as individual patches with a
header containing metadata:
  cvsps -x -b HEAD -g -p ../../patches/
split exported patches into individial files like author data, log, file list:
  for i in `seq 1 546`; do ../parse-cvsps-patch.pl ../patches/$i.patch ;done
apply it to an completely empty git-repo:
  for i in `seq 1 546`; do ../apply.sh ../patches/$i.patch ;done
Stupid scripts are attached. cvsps is here:
  http://www.cobite.com/cvsps/
Kay

← back to recent threads