From: Brandon Casey <drafnel@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Jessica Clarke <jrtc27@jrtc27.com>, git <git@vger.kernel.org>,
Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] config.mak.uname: Define FREAD_READS_DIRECTORIES for GNU/Hurd
Date: Wed, 22 Apr 2020 11:54:31 -0700 [thread overview]
Message-ID: <CA+sFfMdPDuZze76OnwPDm7VjcvSu-nW03+kthHM4trs5KRJ6SQ@mail.gmail.com> (raw)
In-Reply-To: <CA+sFfMfre6W5GcPh1pWcroFD9S9OPj_uLp5CK11yh-UhqgDs2w@mail.gmail.com>
On Wed, Apr 22, 2020 at 11:48 AM Brandon Casey <drafnel@gmail.com> wrote:
> I just wrote a test program and tested on Linux, Darwin, and Windows.
> Linux and Darwin both succeed to fopen() a directory and fail to
> fread() it, as expected. Windows fails to fopen() a directory.
I just want to be clear here, so based on the above, Linux and Darwin
should _not_ need to have FREAD_READS_DIRECTORIES set.
Windows, as always, is a stickier subject. Based on the above, Windows
should not need FREAD_READS_DIRECTORIES either. It's not set when MSVC
is the compiler, but it is set for cygwin.
-Brandon
next prev parent reply other threads:[~2020-04-22 18:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 15:33 [PATCH] config.mak.uname: Define FREAD_READS_DIRECTORIES for GNU/Hurd Jessica Clarke
2020-04-22 16:41 ` Jonathan Nieder
2020-04-22 17:48 ` Junio C Hamano
2020-04-22 18:48 ` Brandon Casey
2020-04-22 18:50 ` Jessica Clarke
2020-04-22 19:05 ` Brandon Casey
2020-04-22 18:54 ` Brandon Casey [this message]
2020-04-22 19:13 ` Brandon Casey
2020-04-22 19:58 ` Jeff King
2020-04-22 21:18 ` Brandon Casey
2020-04-24 5:51 ` Jeff King
2020-04-22 17:18 ` Junio C Hamano
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=CA+sFfMdPDuZze76OnwPDm7VjcvSu-nW03+kthHM4trs5KRJ6SQ@mail.gmail.com \
--to=drafnel@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=jrtc27@jrtc27.com \
--cc=peff@peff.net \
/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).