From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Cc: Brian Downing <bdowning@lavos.net>,
Gordon Heydon <gordon@heydon.com.au>,
git@vger.kernel.org
Subject: Re: git cvsimport branches not consistent with CVS branches
Date: Sun, 8 Jul 2007 12:47:16 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0707081246040.4248@racer.site> (raw)
In-Reply-To: <200707081253.06129.robin.rosenberg.lists@dewire.com>
Hi,
On Sun, 8 Jul 2007, Robin Rosenberg wrote:
> Corecode's fromcvs is pretty fast and incremental and AFAIK accurate.
The only problem is that it is a misnomer: it is not fromcvs, but fromrcs,
since you have to have access at the _files_. This is not always
possible.
Ciao,
Dscho
next prev parent reply other threads:[~2007-07-08 11:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-08 0:45 git cvsimport branches not consistent with CVS branches Gordon Heydon
2007-07-08 5:45 ` Brian Downing
2007-07-08 10:53 ` Robin Rosenberg
2007-07-08 11:47 ` Johannes Schindelin [this message]
2007-07-08 12:22 ` Robin Rosenberg
2007-07-08 21:02 ` Brian Downing
2007-07-08 14:38 ` Steffen Prohaska
2007-07-09 4:31 ` Josh Triplett
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=Pine.LNX.4.64.0707081246040.4248@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=bdowning@lavos.net \
--cc=git@vger.kernel.org \
--cc=gordon@heydon.com.au \
--cc=robin.rosenberg.lists@dewire.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).