Reece, I understand your explanation. But, git-p4 submit does not work for me. Are you able to re-produce the problem? Thanks, Gary --- On Tue, 12/2/08, Reece Dunn <msclrhd@xxxxxxxxxxxxxx> wrote: > From: Reece Dunn <msclrhd@xxxxxxxxxxxxxx> > Subject: Re: git-p4 submit, Can't clobber writable file > To: garyyang6@xxxxxxxxx > Cc: git@xxxxxxxxxxxxxxx > Date: Tuesday, December 2, 2008, 3:51 PM > 2008/12/2 Gary Yang <garyyang6@xxxxxxxxx>: > > > > 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... > > This will be running a `p4 sync ...` command to ensure that > the files > are up-to-date. > > > //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 ... > > Perforce will mark files as readonly when it does a > checkout. When you > use `p4 edit` to say you have made changes to the file, > Perforce > removes the readonly bit. > > What is happening here is that the sync (checkout) command > is trying > to write foo.h/c to your build_scripts directory, but > because they > already exist there *and* are not readonly, Perforce is > producing that > error as it does not want to overwrite any files that have > changed > locally. > > Not sure what is happening on the git-p4 side, though. > > - Reece -- 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
