From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Eric Blake <ebb9@byu.net>, Steffen Prohaska <prohaska@zib.de>,
Jim Meyering <jim@meyering.net>,
m4-patches@gnu.org,
Linus Torvalds <torvalds@linux-foundation.org>,
git@vger.kernel.org
Subject: Re: cvsimport bug on branches [was: conversion to git]
Date: Sat, 22 Sep 2007 01:16:24 +0200 [thread overview]
Message-ID: <200709220116.26369.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0709212212020.28395@racer.site>
fredag 21 september 2007 skrev Johannes Schindelin:
> No, it's yet another dependency. And the quality of the code still
> depends on the programmer, not the language.
I think I can agree there, on both counts. But, if you want a good incremental
CVS importer and have access to the rcs files, that's the one there is.
git-cvsimport has a dependency on cvsps, which isn't included. You have to
to look it up yourself chooing among a dozen unequally bad versions.
Installing ruby isn't any harder.
The dependency excludes it from being included with Git, but it does not
disqualify it as a tool on it's own.
-- robin
next prev parent reply other threads:[~2007-09-21 23:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <loom.20070920T010842-272@post.gmane.org>
2007-09-21 1:17 ` cvsimport bug on branches [was: conversion to git] Eric Blake
2007-09-21 5:18 ` Steffen Prohaska
2007-09-21 15:42 ` Linus Torvalds
2007-09-21 17:15 ` Robin Rosenberg
2007-09-21 20:22 ` Johannes Schindelin
2007-09-21 20:42 ` Robin Rosenberg
2007-09-21 21:12 ` Johannes Schindelin
2007-09-21 23:16 ` Robin Rosenberg [this message]
2007-09-22 8:07 ` fromcvs installation [was: cvsimport bug on branches [was: conversion to git]] Steffen Prohaska
2007-09-22 15:08 ` Simon 'corecode' Schubert
2007-09-22 0:05 ` cvsimport bug on branches [was: conversion to git] Martin Langhoff
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=200709220116.26369.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=ebb9@byu.net \
--cc=git@vger.kernel.org \
--cc=jim@meyering.net \
--cc=m4-patches@gnu.org \
--cc=prohaska@zib.de \
--cc=torvalds@linux-foundation.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).