From: Rostislav Svoboda <rostislav.svoboda@gmail.com>
To: "Kelly F. Hickel" <kfh@mqsoftware.com>
Cc: git@vger.kernel.org
Subject: Re: Best way to merge two repos with same content, different history
Date: Fri, 5 Jun 2009 19:19:51 +0200 [thread overview]
Message-ID: <286817520906051019k78dc002cg8006987a7258b6de@mail.gmail.com> (raw)
In-Reply-To: <63BEA5E623E09F4D92233FB12A9F794303117DC1@emailmn.mqsoftware.com>
On Fri, Jun 5, 2009 at 19:10, Kelly F. Hickel<kfh@mqsoftware.com> wrote:
> Bost,
> Thanks, but I'm already working with a local copy of the CVS repo. I've corresponded with Michael Haggerty about the time this takes, and there just doesn't seem to be any way to improve the speed, without making some fairly drastic changes to cvs2git.
uhm, see below
Bost
On Tue, Feb 3, 2009 at 14:55, Johannes
Schindelin<Johannes.Schindelin@gmx.de> wrote:
>> If you do not have filesystem access to your CVS repository, you might
>> be able to clone it using CVSSuck [2,3].
>
> A substantially faster option would be to go with cvsclone:
>
> http://samba.org/ftp/tridge/rtc/cvsclone.l
>
> (in my case, cvsclone was not only faster, but it actually worked, too,
> which is more than I could say of CVSSuck).
next prev parent reply other threads:[~2009-06-05 17:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 16:30 Best way to merge two repos with same content, different history Kelly F. Hickel
2009-06-05 16:53 ` Rostislav Svoboda
2009-06-05 17:10 ` Kelly F. Hickel
2009-06-05 17:19 ` Rostislav Svoboda [this message]
2009-06-05 18:46 ` Robin H. Johnson
2009-06-05 19:06 ` Best way to merge two repos with same content, differenthistory Kelly F. Hickel
2009-06-05 20:02 ` Robin H. Johnson
2009-06-05 20:08 ` Kelly F. Hickel
2009-06-19 9:52 ` Michael Haggerty
2009-06-05 17:01 ` Best way to merge two repos with same content, different history Avery Pennarun
2009-06-05 17:11 ` Kelly F. Hickel
2009-06-05 17:15 ` Markus Heidelberg
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=286817520906051019k78dc002cg8006987a7258b6de@mail.gmail.com \
--to=rostislav.svoboda@gmail.com \
--cc=git@vger.kernel.org \
--cc=kfh@mqsoftware.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).