From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Johannes Sixt <j6t@kdbg.org>, Pat Thoyts <patthoyts@gmail.com>,
gitster@pobox.com, msysGit <msysgit@googlegroups.com>,
Sebastian Schuberth <sschuberth@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH] Do not trust PWD blindly
Date: Sun, 10 Jul 2011 18:52:36 -0700 [thread overview]
Message-ID: <86k4bpporf.fsf@red.stonehenge.com> (raw)
In-Reply-To: <alpine.DEB.1.00.1107110057120.3379@bonsai2> (Johannes Schindelin's message of "Mon, 11 Jul 2011 00:59:03 +0200 (CEST)")
>>>>> "Johannes" == Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
Johannes> You might be very surprised, but that is not true on the Linux system
Johannes> where one of the 4msysgit.git test cases does _not_ break, while it does
Johannes> on Windows.
If you ever depend on a userspace PWD to be your actual current
directory without at least stat()ing it, you've failed.
In my experience, it is *never* reliable. It's just a hint.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.posterous.com/ for Smalltalk discussion
next prev parent reply other threads:[~2011-07-11 1:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABNJ2GKgzXGDq9FhKcVP380bs=rEKqYdrOaCb+A99_TBm7A4_A@mail.gmail.com>
2011-07-09 17:38 ` [PATCH] Do not trust PWD blindly Johannes Schindelin
2011-07-09 20:06 ` Sebastian Schuberth
2011-07-10 20:47 ` Johannes Sixt
2011-07-10 22:59 ` Johannes Schindelin
2011-07-11 1:52 ` Randal L. Schwartz [this message]
2011-07-11 9:26 ` Johannes Schindelin
2011-07-11 16:56 ` Junio C Hamano
2011-07-11 17:18 ` Johannes Schindelin
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=86k4bpporf.fsf@red.stonehenge.com \
--to=merlyn@stonehenge.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=msysgit@googlegroups.com \
--cc=patthoyts@gmail.com \
--cc=sschuberth@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.
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).