From: Jing Xue <jingxue@digizenstudio.com>
To: Gary Yang <garyyang6@yahoo.com>
Cc: git@vger.kernel.org
Subject: Re: git-p4 submit, Can't clobber writable file
Date: Tue, 2 Dec 2008 22:07:29 -0500 [thread overview]
Message-ID: <20081203030729.GB5624@jabba.hq.digizenstudio.com> (raw)
In-Reply-To: <40586.80065.qm@web37902.mail.mud.yahoo.com>
On Tue, Dec 02, 2008 at 02:30:51PM -0800, Gary Yang wrote:
>
> I followed the instructions at http://modular.math.washington.edu/home/mhansen/git-1.5.5.1/contrib/fast-import/git-p4.txt
>
> But, I am not able to git-p4 submit. Any idea?
>
> git-p4 clone //build/scripts build_scripts
> cd build_scripts
> vi foo.h
> git commit foo.h
> git-p4 rebase
> git-p4 submit
>
> from sets import Set;
> Perforce checkout for depot path //build/scripts/ located at /home/gyang/workspace/build_scripts/
> Syncronizing p4 checkout...
> //build/scripts/foo.h#1 - added as /home/gyang/workspace/build_scripts/foo.h
> Can't clobber writable file /home/gyang/workspace/build_scripts/foo.h
> //build/scripts/foo.c#1 - added as /home/gyang/workspace/build_scripts/foo.c
> Can't clobber writable file /user/home/gyang/workspace/build_scripts/foo.c
> ......
> command failed: p4 sync ...
You might want to clone to a git working dir different than the p4
working dir.
For instance, if your p4 workspace has the working dir set to
build_scripts/, try 'git p4 clone //build/scripts build_scripts.git'.
You would then normally work under build_scripts.git/. build_scripts/
would only be used by git-p4 at submission time.
Cheers.
--
Jing Xue
next prev parent reply other threads:[~2008-12-03 3:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 22:30 git-p4 submit, Can't clobber writable file Gary Yang
2008-12-02 23:51 ` Reece Dunn
2008-12-03 0:14 ` Gary Yang
2008-12-03 3:07 ` Jing Xue [this message]
2008-12-03 6:04 ` Gary Yang
2008-12-03 11:07 ` Arafangion
2008-12-03 19:06 ` Gary Yang
2008-12-03 14:24 ` Jing Xue
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=20081203030729.GB5624@jabba.hq.digizenstudio.com \
--to=jingxue@digizenstudio.com \
--cc=garyyang6@yahoo.com \
--cc=git@vger.kernel.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).