git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Robert Blum" <rob.blum@gmail.com>
Cc: simon@lst.de, shausman@trolltech.com, marius@trolltech.com,
	hanwen@google.com, gitster@pobox.com, git@vger.kernel.org
Subject: Re: [PATCH] git-p4: chdir now properly sets PWD environment variable in msysGit
Date: Sun, 03 Aug 2008 14:13:42 -0700	[thread overview]
Message-ID: <7v7iaxu7i1.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <bad7471c0808011250v569ffaaby9e20a5ba1f971927@mail.gmail.com> (Robert Blum's message of "Fri, 1 Aug 2008 12:50:03 -0700")

"Robert Blum" <rob.blum@gmail.com> writes:

> P4 on Windows expects the PWD environment variable to be set to the
> current working dir, but os.chdir in python doesn't do that by default

Missing full stop at the end of sentence aside, this comment makes me
wonder if there is an optional way to have it set it, as opposed to the
inconvenient way it behaves "by defualt".  If there is none, I think your
patch, even though it looks ugly, is the least evil approach.  Another way
might be to wrap callsites of system() by introducing a "run_p4" function,
like:

	def run_p4(arg):
        	os.environ['PWD'] = os.getcwd() if os.name == 'nt'
		return system(arg)

> ---
>
> Pushing it out to the list since I'm not entirely sure who the git-p4 owner
> even is. CC'ed likely suspects for ownership ;)

Thanks.  I've been waiting for an Ack from somewhere or success reports
from p4 users on Windows.

  reply	other threads:[~2008-08-03 21:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-01 19:50 [PATCH] git-p4: chdir now properly sets PWD environment variable in msysGit Robert Blum
2008-08-03 21:13 ` Junio C Hamano [this message]
     [not found]   ` <bad7471c0808040601y10cceb44idcde5a4a8f415769@mail.gmail.com>
2008-08-04 13:04     ` Fwd: " Robert Blum
2008-08-16  5:44       ` Junio C Hamano
2008-08-16  5:56         ` Junio C Hamano
2008-08-05  8:24   ` Simon Hausmann
2008-08-04  3:06 ` Han-Wen Nienhuys
2008-08-05 22:23 ` Alex Riesen

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=7v7iaxu7i1.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=hanwen@google.com \
    --cc=marius@trolltech.com \
    --cc=rob.blum@gmail.com \
    --cc=shausman@trolltech.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).