From: Andreas Ericsson <ae@op5.se>
To: git@vger.kernel.org
Subject: Re: [PATCH] Fix compilation of git.c
Date: Wed, 16 Nov 2005 07:54:30 +0100 [thread overview]
Message-ID: <437AD7A6.6050906@op5.se> (raw)
In-Reply-To: <7v4q6de1oc.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
>
>>Some systems do not define GLOB_ABORTED and GLOB_NOMATCH.
>
>
> That's true, but the glob does not distinguish executables and
> others anyway, do wouldn't it be more portable and easier to do
> readdir, stat and list in the loop?
>
Got one implementation of that too, but it doesn't sort the command list
and I thought it was nice to have them that way while too lazy to
implement myself.
OTOH, that switch/case thing was for debugging (forgot prefix=/usr when
compiling...). I'm perfectly fine with
if (glob(....)) {
error_out("friendly message");
}
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
prev parent reply other threads:[~2005-11-16 6:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 1:44 [PATCH] Fix compilation of git.c Johannes Schindelin
2005-11-16 3:01 ` Junio C Hamano
2005-11-16 6:54 ` Andreas Ericsson [this message]
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=437AD7A6.6050906@op5.se \
--to=ae@op5.se \
--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).