From: Han-Wen Nienhuys <hanwen@xs4all.nl>
To: Simon Hausmann <simon@lst.de>
Cc: Alex Riesen <raa.lkml@gmail.com>, git@vger.kernel.org
Subject: Re: Asking again... [Re: how to properly import perforce history?]
Date: Mon, 11 Jun 2007 22:19:05 -0300 [thread overview]
Message-ID: <466DF489.7010700@xs4all.nl> (raw)
In-Reply-To: <200706112346.13628.simon@lst.de>
Simon Hausmann escreveu:
>> system("p4 revert %s" % f)
>> system("p4 delete %s" % f)
>
> Ooops, indeed. Makes me realizes that I've never actually submitted files with
> spaces in the name :). For now I've quoted them with double quotes like in
> the other places, which is better than nothing. Thanks for spotting!
>>> import commands
>>> commands.mkarg ('$foo bar')
" '$foo bar'"
--
Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen
next prev parent reply other threads:[~2007-06-12 1:22 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
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 [this message]
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=466DF489.7010700@xs4all.nl \
--to=hanwen@xs4all.nl \
--cc=git@vger.kernel.org \
--cc=raa.lkml@gmail.com \
--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).