git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Anyone working on a CVS->git converter?
Date: Tue, 03 May 2005 02:28:59 +0200	[thread overview]
Message-ID: <1115080139.21105.18.camel@localhost.localdomain> (raw)
In-Reply-To: <4275857A.1050106@zytor.com>

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

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

[-- Attachment #2: apply.sh --]
[-- Type: application/x-shellscript, Size: 564 bytes --]

[-- Attachment #3: parse-cvsps-patch.pl --]
[-- Type: application/x-perl, Size: 1528 bytes --]

      parent reply	other threads:[~2005-05-03  0:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-02  1:42 Anyone working on a CVS->git converter? H. Peter Anvin
2005-05-02 16:11 ` Juliusz Chroboczek
2005-05-03  0:28 ` Kay Sievers [this message]

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=1115080139.21105.18.camel@localhost.localdomain \
    --to=kay.sievers@vrfy.org \
    --cc=git@vger.kernel.org \
    --cc=hpa@zytor.com \
    /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).