From: Marius Storm-Olsen <marius@trolltech.com>
To: Scott Lamb <slamb@slamb.org>
Cc: Simon Hausmann <simon@lst.de>, Junio C Hamano <junkio@cox.net>,
git@vger.kernel.org
Subject: Re: git-p4import.py robustness changes
Date: Mon, 04 Jun 2007 10:41:34 +0200 [thread overview]
Message-ID: <4663D03E.5040601@trolltech.com> (raw)
In-Reply-To: <839AEF71-ED29-4A79-BE97-C79EAFEDC466@slamb.org>
[-- Attachment #1: Type: text/plain, Size: 811 bytes --]
> git-p4import.py should work fine on Windows, too - the binary mode on
> the pipe should be all handled by "subprocess", and git-p4's
> data.replace("\r\n", "\n") is not necessary if you use "LineEnd:
> unix" or "share" in the Perforce client specification.
The problem is that you cannot set the LineEnd when using the 'p4
print' command, since it doesn't use the client spec; so Perforce the
uses the platform default when printing the file.
> git-p4 seems to use "git fast-import". I guess the big performance
> improvement there is removing the ls-files operation? So we're
> talking about a 0-10% speedup, right? Plus some fork()/exec()
> overhead.
With git-p4 the performance bottleneck is from what we can see the
Perforce server, on non-Windows machines.
--
.marius
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 187 bytes --]
next prev parent reply other threads:[~2007-06-04 8:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 16:47 git-p4import.py robustness changes Scott Lamb
2007-05-31 23:53 ` Junio C Hamano
2007-06-02 20:41 ` Scott Lamb
2007-06-02 21:33 ` Junio C Hamano
2007-06-02 23:21 ` Scott Lamb
2007-06-02 23:52 ` Junio C Hamano
2007-06-03 13:11 ` Simon Hausmann
2007-06-03 20:12 ` Scott Lamb
2007-06-04 5:54 ` Shawn O. Pearce
2007-06-04 6:09 ` Dana How
2007-06-04 6:18 ` Shawn O. Pearce
2007-06-04 7:19 ` Scott Lamb
2007-06-05 7:21 ` Simon Hausmann
2007-06-04 8:41 ` Marius Storm-Olsen [this message]
2007-06-04 5:56 ` Shawn O. Pearce
2007-06-12 21:46 ` Simon Hausmann
2007-06-13 21:06 ` Scott Lamb
2007-06-13 22:34 ` Simon Hausmann
2007-06-14 5:35 ` Shawn O. Pearce
2007-06-14 21:44 ` Simon Hausmann
2007-06-15 3:13 ` Shawn O. Pearce
2007-06-15 5:30 ` Marius Storm-Olsen, mstormo_git
2007-06-03 3:58 ` [PATCH 1/4] git-p4import: fix subcommand error handling Scott Lamb
2007-06-03 3:58 ` [PATCH 2/4] git-p4import: use lists of subcommand arguments Scott Lamb
2007-06-03 3:58 ` [PATCH 3/4] git-p4import: resume on correct p4 changeset Scott Lamb
2007-06-03 3:58 ` [PATCH 4/4] git-p4import: partial history Scott Lamb
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=4663D03E.5040601@trolltech.com \
--to=marius@trolltech.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=simon@lst.de \
--cc=slamb@slamb.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).