From: "Robert Blum" <rob.blum@gmail.com>
To: git@vger.kernel.org
Subject: Fwd: [PATCH] git-p4: chdir now properly sets PWD environment variable in msysGit
Date: Mon, 4 Aug 2008 06:04:59 -0700 [thread overview]
Message-ID: <bad7471c0808040604p6de570f1k35aa4e76757ca6fd@mail.gmail.com> (raw)
In-Reply-To: <bad7471c0808040601y10cceb44idcde5a4a8f415769@mail.gmail.com>
Forgot reply-all - forwarding to list....
> 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".
Not that I'm aware of. My 'by default' comment refers to a default
Python installation, i.e. unpatched. As far as I know, the real
culprit in this is p4. I'd argue it's a bug, since they should be
using getcwd(), not getpwd(). Moot point - I don't want to wait for
git-p4 until I have convinced perforce to fix this and a new p4 rolls
around ;)
> If there is none, I think your
> patch, even though it looks ugly, is the least evil approach.
Warms the cockles of my heart ;)
> 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)
Happy to submit a new patch with that, if that's preferred.
> Thanks. I've been waiting for an Ack from somewhere or success reports
> from p4 users on Windows.
Han-Wen seems OK with it. (BTW: Who *is* the maintainer of git-p4?)
But hold off on applying - I'll resubmit with the run_p4 approach
today.
(Oh, and of course: Works for me ;)
- Robert
next prev parent reply other threads:[~2008-08-04 13:06 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
[not found] ` <bad7471c0808040601y10cceb44idcde5a4a8f415769@mail.gmail.com>
2008-08-04 13:04 ` Robert Blum [this message]
2008-08-16 5:44 ` Fwd: " 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=bad7471c0808040604p6de570f1k35aa4e76757ca6fd@mail.gmail.com \
--to=rob.blum@gmail.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).