From: "Ping Yin" <pkufranky@gmail.com>
To: "Michael Haggerty" <mhagger@alum.mit.edu>
Cc: "David Mansfield" <david@cobite.com>,
"Steffen Prohaska" <prohaska@zib.de>,
git@vger.kernel.org
Subject: Re: [PATCH] cvsps/cvsimport: fix branch point calculation and broken branch imports
Date: Sun, 27 Apr 2008 13:06:53 +0800 [thread overview]
Message-ID: <46dff0320804262206p76941ee8la6a784ed0b6f8294@mail.gmail.com> (raw)
In-Reply-To: <47FC2190.3070303@alum.mit.edu>
On Wed, Apr 9, 2008 at 9:53 AM, Michael Haggerty <mhagger@alum.mit.edu> wrote:
> > The place where the fixup branch logic needs to be is in git-cvsimport,
> > not in cvsps. Better yet, get rid of git-cvsimport and replace it with
> > cvs2git if it works better.
>
> cvs2git hopefully gives a more accurate conversion of a CVS repository
> -- it handles all of the cases described above, plus many more [1] --
> but it is much slower and can't work incrementally. So there is
> definitely still demand for something like git-cvsimport.
>
These days i tried to convert the cvs repository into git. I really
want the conversion to be as accurate as possible. However, the cvs
repository has been tagged in a very bad style which makes
git-cvsimport or cvsps not work well.
cvs2git sounds to be the right tool i should try. Unfortualely, i
can't touch the cvs repository directly. So is it possible to use
cvs2git in the remote host instead of the host of the cvs repository
just as git-cvsimport does? Yes, i know it can't now. I just wonder
whether it is possible to implement.
I choose to reply to this thread instead of opening a new one because
i think this reply of Michael has told much shortcommings of
git-cvsimport or cvsps but had got no replies yet.
--
Ping Yin
next prev parent reply other threads:[~2008-04-27 5:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 1:34 [PATCH] cvsps/cvsimport: fix branch point calculation and broken branch imports David Mansfield
2008-04-02 19:29 ` Junio C Hamano
2008-04-03 1:44 ` David Mansfield
2008-04-03 2:06 ` Junio C Hamano
2008-04-03 2:27 ` David Mansfield
2008-04-03 5:47 ` Steffen Prohaska
2008-04-03 13:49 ` David Mansfield
2008-04-04 9:52 ` Michael Haggerty
2008-04-07 17:54 ` David Mansfield
2008-04-07 18:07 ` Jean-François Veillette
2008-04-09 1:53 ` Michael Haggerty
2008-04-27 5:06 ` Ping Yin [this message]
2008-04-27 5:47 ` Michael Haggerty
2008-04-27 5:51 ` Ping Yin
2008-04-27 7:38 ` Ping Yin
2008-04-27 7:43 ` Ping Yin
2008-04-27 7:48 ` Ping Yin
2008-04-27 8:48 ` Ping Yin
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=46dff0320804262206p76941ee8la6a784ed0b6f8294@mail.gmail.com \
--to=pkufranky@gmail.com \
--cc=david@cobite.com \
--cc=git@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
--cc=prohaska@zib.de \
/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).