git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Pearce <spearce@spearce.org>
To: Ian Zimmerman <itz@buug.org>
Cc: git@vger.kernel.org
Subject: Re: fast-import: multiple processes possible?
Date: Sat, 27 Nov 2010 14:28:17 -0800	[thread overview]
Message-ID: <AANLkTi=ZH+GNZyPSbafuDEE5nsFtezoePK+gFtM6HrEX@mail.gmail.com> (raw)
In-Reply-To: <8739qmzaha.fsf@matica.localdomain>

On Sat, Nov 27, 2010 at 2:07 PM, Ian Zimmerman <itz@buug.org> wrote:
>
> Hi, I have a user question, I hope that's ok.  Actually, the end goal is
> development of a fast-import frontend.  The fast-import manpage says
> that it is safe to run "any other" git operation concurrently with
> fast-import.  It doesn't say if it is possible and safe to run another
> copy of fast-import itself.

Yes, you can.

The only problem is, each fast-import cannot see the objects created
by the other concurrent fast-imports until they either terminate, or
execute "checkpoint" command received from the frontend.

-- 
Shawn.

      reply	other threads:[~2010-11-27 22:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-27 22:07 fast-import: multiple processes possible? Ian Zimmerman
2010-11-27 22:28 ` Shawn Pearce [this message]

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='AANLkTi=ZH+GNZyPSbafuDEE5nsFtezoePK+gFtM6HrEX@mail.gmail.com' \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=itz@buug.org \
    /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).