From: Michal Rokos <michal.rokos@nextsoft.cz>
To: Junio C Hamano <gitster@pobox.com>
Cc: GIT <git@vger.kernel.org>
Subject: Re: [PATCH] Configure test for FREAD_READS_DIRECTORIES
Date: Tue, 4 Mar 2008 12:48:53 +0100 [thread overview]
Message-ID: <200803041248.54197.michal.rokos@nextsoft.cz> (raw)
In-Reply-To: <7v7igi911y.fsf@gitster.siamese.dyndns.org>
Hello,
On Tuesday 04 March 2008 12:32:57 Junio C Hamano wrote:
> Michal Rokos <michal.rokos@nextsoft.cz> writes:
> >> On how many different platforms was this configure check tested on?
> >
> > Test works on Linux (no FREAD_READS_DIRECTORIES) and HPUXes
> > (FREAD_READS_DIRECTORIES): HP-UX B.11.23 ia64 (Itanium) and HP-UX B.11.11
> > 9000/800 (PaRisc)
> >
> > Do you want me to resend with "."?
>
> Probably resending with "." and asking the list audiences for help in
> testing would help you gather success reports on different platforms.
Will do... Did that.
Do you think that there's some reason not-to merge it? I mean if fopen(".")
throws an error, FREAD_READS_DIRECTORIES will NOT be defined - as is it now.
I don't know how many people cares about configure script since there are
missing bits in it again and again. I believe it could receive good amount of
testing only when it's merged in.
I'm trying to make GIT working on HPUX - next patch in my queue is about
broken vsnprintf() that returns -1 on maxsize overrun. Do you think that it's
more likely that patch will be accepted when I omit "broken vsnprintf()"
detection code from configure.ac?
MR
--
Michal Rokos
NextSoft s.r.o.
Vyskočilova 1/1410
140 21 Praha 4
phone: +420 267 224 311
fax: +420 267 224 307
mobile: +420 736 646 591
e-mail: michal.rokos@nextsoft.cz
next prev parent reply other threads:[~2008-03-04 11:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 9:48 [PATCH] Configure test for FREAD_READS_DIRECTORIES Michal Rokos
2008-03-04 11:03 ` Junio C Hamano
2008-03-04 11:17 ` Michal Rokos
2008-03-04 11:32 ` Junio C Hamano
2008-03-04 11:48 ` Michal Rokos [this message]
2008-03-04 12:17 ` Jakub Narebski
2008-03-05 17:57 ` 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=200803041248.54197.michal.rokos@nextsoft.cz \
--to=michal.rokos@nextsoft.cz \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).