From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: failing to send patches to the list
Date: Sat, 14 Jul 2007 02:58:45 +0200 [thread overview]
Message-ID: <f79742$j44$2@sea.gmane.org> (raw)
In-Reply-To: 20070713093050.GA18001@lapse.madduck.net
martin f krafft wrote:
> Subject: [PATCH] fall back to mozilla's sha.h if openssl/sha.h is not available
>
> Uses $(CPP) to attempt to preprocess an include <openssl/sha.h> directive. If
> that fails, NO_OPENSSL is defined, causing the Makefile to fall back to using
> mozilla's SHA implementation.
Shouldn't this be rather in configure.in? Main Makefile has only defaults
for different systems, but does not do tests.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2007-07-14 0:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 9:30 failing to send patches to the list martin f krafft
2007-07-13 9:56 ` git-svn patch faulty (was: failing to send patches to the list) martin f krafft
2007-07-14 10:54 ` Eric Wong
2007-07-13 12:57 ` failing to send patches to the list Alex Riesen
2007-07-14 6:05 ` martin f krafft
2007-07-13 15:55 ` Jeff King
2007-07-14 6:52 ` martin f krafft
2007-07-14 0:58 ` Jakub Narebski [this message]
2007-07-14 6:59 ` martin f krafft
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='f79742$j44$2@sea.gmane.org' \
--to=jnareb@gmail.com \
--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).