From: Sam Vilain <sam@vilain.net>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: Jakub Narebski <jnareb@gmail.com>,
Arnaud Bailly <abailly@oqube.com>,
git@vger.kernel.org
Subject: Re: From P4 to Git
Date: Mon, 03 Aug 2009 23:30:10 +1200 [thread overview]
Message-ID: <1249299010.7164.8.camel@maia.lan> (raw)
In-Reply-To: <81b0412b0908030147i34a7440dg982c7a6e7dc51bca@mail.gmail.com>
On Mon, 2009-08-03 at 10:47 +0200, Alex Riesen wrote:
> Is it an import-once tool, or can the process be restarted? (because it looks
> like the script needs a complicated setup).
It's fully restartable. Not only that but it uses transaction
protection to make sure that its internal state doesn't get corrupted
when performing the various options.
> Can it be used from a client machine?
> And more importantly:
> can the branches be found from incomplete history,
> restricted by path and changelist range? (because, in a corporate
> setup, clients seldom have full access to all data).
No, it's server only. I think I did get around to implementing not having
to go through all the stages for branches you didn't care to import. It's
difficult though, the stage which correlates those thousands of 'integrate'
records is never going to be fast. Be prepared to tune your postgres - add
lots of shared_buffers and sort memory if your project is as large as Perl.
Sam.
next prev parent reply other threads:[~2009-08-03 11:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 20:14 From P4 to Git Arnaud Bailly
2009-07-28 20:32 ` david
2009-07-28 21:10 ` Jakub Narebski
[not found] ` <85r5vxbd8e.fsf@oqube.com>
2009-07-31 9:22 ` Jakub Narebski
2009-07-31 11:14 ` Alex Riesen
2009-08-03 7:49 ` Sam Vilain
2009-08-03 8:47 ` Alex Riesen
2009-08-03 11:30 ` Sam Vilain [this message]
2009-08-03 13:50 ` Alex Riesen
2009-08-03 20:32 ` Sam Vilain
2009-08-03 21:51 ` Alex Riesen
2009-08-04 0:29 ` Sam Vilain
2009-08-02 7:16 ` Sam Vilain
2009-08-04 12:31 ` Arnaud Bailly
2009-08-04 12:35 ` Peter Baumann
2009-08-03 21:37 ` John Tapsell
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=1249299010.7164.8.camel@maia.lan \
--to=sam@vilain.net \
--cc=abailly@oqube.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=raa.lkml@gmail.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).