From: Keith Packard <keithp@keithp.com>
To: Git Mailing List <git@vger.kernel.org>
Cc: keithp@keithp.com
Subject: parsecvs tool now creates git repositories
Date: Sat, 01 Apr 2006 21:36:28 -0800 [thread overview]
Message-ID: <1143956188.2303.39.camel@neko.keithp.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 956 bytes --]
I've hacked in cheesy system(3) calls to invoke various git tools to
create a git repository from a parsed cvs repository. It's about the
same speed as git-cvsimport now.
The UI is a total disaster, sufficient for testing. You must create an
Authors file in the current directory which looks like the git-cvsimport
authors file. You must also have a edit-change-log program in your path
which edits the commit message in place. /bin/true will work if you
don't need to edit the messages.
I should clearly steal the existing git-cvsimport command line arguments
and use those.
This tool successfully, and usefully, imports the X.org xserver CVS
repository, along with correctly importing several other repositories
I've tried. It doesn't quite manage to compute correct branch points for
the postgresql CVS repository, so there is clearly work remaining to be
done.
CVS - your code's worst nightmare.
--
keith.packard@intel.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
next reply other threads:[~2006-04-02 5:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-02 5:36 Keith Packard [this message]
2006-04-02 9:39 ` parsecvs tool now creates git repositories Jan-Benedict Glaw
2006-04-02 19:31 ` Jan-Benedict Glaw
2006-04-03 4:10 ` Keith Packard
2006-04-03 4:38 ` Linus Torvalds
2006-04-03 7:25 ` Jan-Benedict Glaw
2006-04-03 13:58 ` Erik Mouw
2006-04-03 16:54 ` Keith Packard
2006-04-03 22:19 ` Keith Packard
2006-04-03 14:03 ` Erik Mouw
2006-04-03 14:21 ` Jakub Narebski
2006-04-03 14:39 ` Keith Packard
2006-04-03 14:37 ` Keith Packard
2006-04-03 15:32 ` Jeff King
2006-04-04 0:55 ` Anand Kumria
2006-04-03 22:38 ` Martin Langhoff
2006-04-04 2:07 ` Keith Packard
2006-04-04 2:16 ` Martin Langhoff
2006-04-04 2:24 ` Keith Packard
2006-04-04 2:42 ` Martin Langhoff
2006-04-04 3:51 ` Keith Packard
2006-04-04 6:09 ` Junio C Hamano
[not found] <20060405174247.GA29758@blackbean.org>
[not found] ` <1144262498.2303.231.camel@neko.keithp.com>
2006-04-06 6:36 ` Fixes to parsecvs Keith Packard
2006-04-06 18:15 ` parsecvs tool now creates git repositories Jim Radford
2006-04-06 20:12 ` Keith Packard
2006-04-06 21:51 ` Martin Langhoff
2006-04-06 22:19 ` Keith Packard
2006-04-06 23:22 ` Martin Langhoff
2006-04-07 7:24 ` Keith Packard
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=1143956188.2303.39.camel@neko.keithp.com \
--to=keithp@keithp.com \
--cc=git@vger.kernel.org \
/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).