From: Alex Riesen <raa.lkml@gmail.com>
To: Simon Hausmann <simon@lst.de>
Cc: git@vger.kernel.org
Subject: Re: Asking again... [Re: how to properly import perforce history?]
Date: Mon, 11 Jun 2007 22:12:32 +0200 [thread overview]
Message-ID: <20070611201232.GA4649@steel.home> (raw)
In-Reply-To: <200706112042.16331.simon@lst.de>
Simon Hausmann, Mon, Jun 11, 2007 20:42:12 +0200:
> On Monday 11 June 2007 17:44:04 Alex Riesen wrote:
> > On 6/11/07, Simon Hausmann <simon@lst.de> wrote:
> > > *plug* You could try with git-p4 from http://repo.or.cz/w/fast-export.git
> > > . It should be just a matter of calling
> > >
> > > git-p4 clone //depot/path
> >
> > Can I suggest you add a target directory mapping to your tool?
> > Something like:
> >
> > git-p4 clone //depot/project/path [libs/project/path] [rev-range]
>
> I'm not sure I understand the libs/project/path part, ...
Your client contains the mappings. It defines how the pathnames on the
p4 server relate to that on your computer. In the example above file
from the depot path //depot/project/path can be found in the directory
of the p4 client in the subdirectories libs/project/path.
> Han-Wen implemented also support for importing multiple depot paths at the
> same time (and tracking them in one git branch).
And where does he put the depot paths? As they are in depot? How does
this corelate to the setups done by genuine P4 users (the poor souls)
where the mappings are not always 1-to-1 right from the root? Or you
haven't got any?
> The environment I'm working in is not too big and fairly liberal and
> reasonably disciplined.
You must be very strange environment indeed. Carefully balanced.
> > And, BTW, don't you have a small problem with filenames with
> > spaces and quoting?
>
> I'm not aware of any problems. For example in our depot we have filenames with
> spaces in them and they appear just fine in my git import. Did you run into
> any specific case? It could very well be that there's a bug somewhere that
> I'm just not hitting myself, so I'm curious :)
No, I just looking at the source. Does python have some magic for
running programs with system() when passed a format string? Like here:
for f in filesToAdd:
system("p4 add %s" % f)
for f in filesToDelete:
system("p4 revert %s" % f)
system("p4 delete %s" % f)
BTW, sometimes you quote the names, but obviously wrong (think about
filenames containing double quotes):
system("p4 edit \"%s\"" % path)
editedFiles.add(path)
next prev parent reply other threads:[~2007-06-11 20:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 20:22 how to properly import perforce history Kevin Green
2007-06-11 14:25 ` Asking again... [Re: how to properly import perforce history?] Kevin Green
2007-06-11 14:56 ` Simon Hausmann
2007-06-11 15:44 ` Alex Riesen
2007-06-11 18:42 ` Simon Hausmann
2007-06-11 20:12 ` Alex Riesen [this message]
2007-06-11 21:20 ` Scott Lamb
2007-06-11 23:16 ` Alex Riesen
2007-06-11 23:41 ` Scott Lamb
2007-06-11 21:46 ` Simon Hausmann
2007-06-12 1:19 ` Han-Wen Nienhuys
2007-06-12 14:12 ` Alex Riesen
2007-06-11 16:41 ` Kevin Green
2007-06-11 20:28 ` Alex Riesen
[not found] ` <20070611194450.GK25093@menevado.ms.com>
[not found] ` <200706112159.34181.simon@lst.de>
2007-06-11 20:51 ` [PATCH] git-p4: check for existence of repo dir before trying to create [Was: Asking again... [Re: how to properly import perforce history?]] Kevin Green
2007-06-11 21:32 ` Simon Hausmann
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=20070611201232.GA4649@steel.home \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=simon@lst.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).