git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Haggerty <mhagger@alum.mit.edu>
To: Ping Yin <pkufranky@gmail.com>
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 07:47:37 +0200	[thread overview]
Message-ID: <48141379.9030306@alum.mit.edu> (raw)
In-Reply-To: <46dff0320804262206p76941ee8la6a784ed0b6f8294@mail.gmail.com>

Ping Yin wrote:
> 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.

cvs2svn/cvs2git itself can't work with remote repositories.  It would be
enough if you could just get a copy of the repository; obviously you
don't need to use the original.

If you can't get a copy of the CVS repository directly, you might be
able to recreate it indirectly via information read over the CVS
protocol using a tool like CVSsuck [1,2].  I have no experience with
CVSsuck, so if you try it out, please let us know whether you were
successful.

Presumably some CVSsuck-like functionality could be built directly into
cvs2git, but given that this request hasn't come up very often and that
the two tools can presumably be used in concert, it doesn't seem worth
the effort.

Michael

[1] http://cvs.m17n.org/~akr/cvssuck/
[2] http://cvs2svn.tigris.org/faq.html#repoaccess

  reply	other threads:[~2008-04-27  5:48 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
2008-04-27  5:47             ` Michael Haggerty [this message]
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=48141379.9030306@alum.mit.edu \
    --to=mhagger@alum.mit.edu \
    --cc=david@cobite.com \
    --cc=git@vger.kernel.org \
    --cc=pkufranky@gmail.com \
    --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).