I would argue that's a bug with git-p4, however that is a warning given by perforce, thus, you should be able to work around it by changing the clientspec, change the clientspec so that it will clobber such files, you will need to refer to the perforce docs for info about that. On Tue, 2008-12-02 at 22:04 -0800, Gary Yang wrote: > So, I have to keep two copies of source tree at my home directory. One is for Perforce build_scripts workspace, another is for Git build_scripts.git. I normally work at build_scripts.git. But, when I need to submit changes to Perforce, I have to copy changed code from build_scripts.git to build_scripts. Then, p4 submit code into Perforce. Is this the only way of using git-p4? > Note: I cannot use git-p4 submit at build_scripts. It claims "Cannot clobber writable file". Is it a bug of git-p4 or the instruction is not correct? > > > --- On Tue, 12/2/08, Jing Xue <jingxue@xxxxxxxxxxxxxxxxx> wrote: > > > From: Jing Xue <jingxue@xxxxxxxxxxxxxxxxx> > > Subject: Re: git-p4 submit, Can't clobber writable file > > To: "Gary Yang" <garyyang6@xxxxxxxxx> > > Cc: git@xxxxxxxxxxxxxxx > > Date: Tuesday, December 2, 2008, 7:07 PM > > 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 > > > > -- > To unsubscribe from this list: send the line "unsubscribe git" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
