From: "H.Merijn Brand" <h.m.brand@xs4all.nl>
To: "H.Merijn Brand" <h.m.brand@xs4all.nl>
Cc: Brandon Casey <casey@nrlssc.navy.mil>,
Junio C Hamano <gitster@pobox.com>,
Morten Welinder <mwelinder@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] Add compat/fopen.c which returns NULL on attempt to open directory
Date: Mon, 11 Feb 2008 11:15:37 +0100 [thread overview]
Message-ID: <20080211111537.2bf47448@pc09.procura.nl> (raw)
In-Reply-To: <20080211102950.122ba93d@pc09.procura.nl>
On Mon, 11 Feb 2008 10:29:50 +0100, "H.Merijn Brand" <h.m.brand@xs4all.nl>
wrote:
> On Fri, 08 Feb 2008 20:32:47 -0600, Brandon Casey <casey@nrlssc.navy.mil>
> wrote:
>
> > Some systems do not fail as expected when fread et al. are called on
> > a directory stream. Replace fopen on such systems which will fail
> > when the supplied path is a directory.
>
> I applied this patch instead of mine, and added the Makefile define
> Harder to trace, as it is not issuing error messages, but could this
> success^Wfailure be related?
No, it is not. Some shell weirdness. This fixes it. Don't know off-hand
if it is portable enough
diff -pur a/t/t5701-clone-local.sh b/t/t5701-clone-local.sh
--- a/t/t5701-clone-local.sh 2008-02-02 05:09:01 +0100
+++ b/t/t5701-clone-local.sh 2008-02-11 11:13:26 +0100
@@ -37,8 +37,8 @@ test_expect_success 'local clone from x'
test_expect_success 'local clone from x.git that does not exist' '
cd "$D" &&
- if git clone -l -s x.git z
- then
+ git clone -l -s x.git z
+ if $? ; then
echo "Oops, should have failed"
false
else
--
H.Merijn Brand Amsterdam Perl Mongers (http://amsterdam.pm.org/)
using & porting perl 5.6.2, 5.8.x, 5.10.x on HP-UX 10.20, 11.00, 11.11,
& 11.23, SuSE 10.1 & 10.2, AIX 5.2, and Cygwin. http://qa.perl.org
http://mirrors.develooper.com/hpux/ http://www.test-smoke.org
http://www.goldmark.org/jeff/stupid-disclaimers/
next prev parent reply other threads:[~2008-02-11 10:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 16:46 [PATCH] opening files in remote.c should ensure it is opening a file H.Merijn Brand
2008-02-08 17:25 ` Mike Ralphson
2008-02-08 20:04 ` H.Merijn Brand
2008-02-18 9:10 ` H.Merijn Brand
2008-02-18 9:30 ` Junio C Hamano
2008-02-18 11:31 ` H.Merijn Brand
2008-02-08 20:36 ` Daniel Barkalow
2008-02-08 20:44 ` Johannes Schindelin
2008-02-09 5:27 ` Junio C Hamano
2008-02-09 5:54 ` Daniel Barkalow
2008-02-08 20:09 ` Junio C Hamano
2008-02-08 20:38 ` Johannes Schindelin
2008-02-09 10:03 ` H.Merijn Brand
2008-02-08 20:15 ` Morten Welinder
2008-02-08 20:33 ` Junio C Hamano
2008-02-08 20:40 ` Johannes Schindelin
2008-02-08 21:19 ` Junio C Hamano
2008-02-08 21:47 ` Johannes Schindelin
2008-02-08 20:58 ` Brandon Casey
2008-02-08 21:14 ` Brandon Casey
2008-02-09 5:12 ` Junio C Hamano
2008-02-09 1:20 ` Brandon Casey
2008-02-09 2:32 ` [PATCH] Add compat/fopen.c which returns NULL on attempt to open directory Brandon Casey
2008-02-11 9:29 ` H.Merijn Brand
2008-02-11 10:15 ` H.Merijn Brand [this message]
2008-02-12 0:20 ` Junio C Hamano
2008-02-12 15:27 ` H.Merijn Brand
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=20080211111537.2bf47448@pc09.procura.nl \
--to=h.m.brand@xs4all.nl \
--cc=casey@nrlssc.navy.mil \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mwelinder@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).