git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
KSKay Sievers <kay.sievers@vrfy.org>
Date
May 3, 2005, 00:28 UTC
Message-ID
<1115080139.21105.18.camel@localhost.localdomain>
In-Reply-To
<4275857A.1050106@zytor.com>
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
Previous: Juliusz Chroboczek
Message 3 of 3 in “Anyone working on a CVS->git converter?”
  1. H. Peter AnvinMay 2, 2005
  2. Juliusz ChroboczekMay 2, 2005
  3. Kay SieversMay 3, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.