git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Tor Arvid Lund <torarvid@gmail.com>
To: Maxim Gordienko <mgordienko@gmail.com>
Cc: Marius Storm-Olsen <marius@trolltech.com>, git@vger.kernel.org
Subject: Re: [GIT-P4] usage under Windows
Date: Sat, 01 Mar 2008 12:44:39 +0100	[thread overview]
Message-ID: <B929D1FF-BAF7-4595-9DAF-07E62B90D767@gmail.com> (raw)
In-Reply-To: <96c268400802291048u31a2d8b6ub1726ade941afb8c@mail.gmail.com>

On 29. feb.. 2008, at 19.48, Maxim Gordienko wrote:

> Thank you, Marius for detailed instructions!
> Now everything except submitting back to perforce works like a charm.
> Perforce complains about git-p4 checkout is not under it's root
>
> Synchronizing p4 checkout...
> executing p4 sync ...
> Path 'c:/tmp/p42/main\...' is not under client's root 'c:\p4'.

I have seen it too. I'm not sure, but it seems to me like even though  
the git-p4 script does a chdir(<perforce_dir>) before calling "p4  
<command> <args>" the chdir is "not seen by" p4 on windows.

I have a patch on my machine where i simply change all the p4 calls,  
like so:

system("p4 sync ...") --> system("p4 sync %s..." % self.clientPath)

This seems to work in all cases, and also in Mac OS X... I can  
probably clean the patch up a bit, and submit it later today or  
tomorrow if you're interested.

      -- Tor Arvid

  parent reply	other threads:[~2008-03-01 12:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-22  6:44 [GIT-P4] usage under Windows Maxim Gordienko
2008-02-27 22:32 ` Marius Storm-Olsen
2008-02-29 18:48   ` Maxim Gordienko
2008-02-29 21:54     ` Marius Storm-Olsen
2008-03-01  7:41       ` Maxim Gordienko
2008-03-01  9:50         ` Marius Storm-Olsen
2008-03-01 11:44     ` Tor Arvid Lund [this message]
2008-03-01 15:53       ` Marius Storm-Olsen
2008-03-03 19:24         ` Maxim Gordienko

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=B929D1FF-BAF7-4595-9DAF-07E62B90D767@gmail.com \
    --to=torarvid@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=marius@trolltech.com \
    --cc=mgordienko@gmail.com \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).