From: Robert Schiele <rschiele@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] add option to find zlib in custom path
Date: Wed, 1 Aug 2007 03:01:56 +0200 [thread overview]
Message-ID: <20070801010156.GF29424@schiele.dyndns.org> (raw)
In-Reply-To: <20070729183545.GC29424@schiele.dyndns.org>
[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]
On Sun, Jul 29, 2007 at 08:35:45PM +0200, Robert Schiele wrote:
> Some systems do not provide zlib development headers and libraries in
> default search path of the compiler. For these systems we should allow
> specifying the location by --with-zlib=PATH or by setting ZLIB_PATH in
> the makefile.
Just wanted to ping about that patch I sent. After I did not get any response
on earlier patches I sent I found that they did not comply to the patch
submission policy. Thus I did this one according to the policy (as far as I
understand it but still don't get any reply.
So I just wanted to ask what's the cause of that?
Didn't you just have time to look at it?
Did I do something wrong? In that case it would be useful if I knew what it
is.
Any other reason?
I mean if it is a timing issue it is not a big issue. Just wanted to know
whether it does make sense to submit more patches or if they all get lost for
some reason I am currently not aware of.
Robert
--
Robert Schiele
Dipl.-Wirtsch.informatiker mailto:rschiele@gmail.com
"Quidquid latine dictum sit, altum sonatur."
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-08-01 1:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-29 18:35 [PATCH] add option to find zlib in custom path Robert Schiele
2007-08-01 1:01 ` Robert Schiele [this message]
2007-08-01 1:06 ` Junio C Hamano
2007-08-01 1:21 ` Robert Schiele
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=20070801010156.GF29424@schiele.dyndns.org \
--to=rschiele@gmail.com \
--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).