From: David Aguilar <davvid@gmail.com>
To: Nicolas Pitre <nico@cam.org>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH v2] remove ARM and Mozilla SHA1 implementations
Date: Mon, 17 Aug 2009 22:49:15 -0700 [thread overview]
Message-ID: <20090818054913.GB37966@gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0908172007590.6044@xanadu.home>
On Mon, Aug 17, 2009 at 08:09:56PM -0400, Nicolas Pitre wrote:
>
> Makefile | 26 +------
>
> -ifneq (,$(findstring arm,$(uname_M)))
> - ARM_SHA1 = YesPlease
> - NO_MKSTEMPS = YesPlease
> -endif
When I added NO_MKSTEMPS I was being conservative when defining
it on arm (I wasn't able to test that platform).
Looks like it wasn't needed afterall.
Thanks.
--
David
next prev parent reply other threads:[~2009-08-18 5:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 23:56 [PATCH] remove ARM and Mozilla SHA1 implementations Nicolas Pitre
2009-08-18 0:09 ` Johannes Schindelin
2009-08-24 4:12 ` Nicolas Pitre
2009-08-24 11:33 ` Johannes Schindelin
2009-08-24 16:52 ` Johannes Schindelin
2009-08-24 17:27 ` Nicolas Pitre
2009-08-24 20:10 ` Peter Harris
2009-08-18 0:09 ` [PATCH v2] " Nicolas Pitre
2009-08-18 5:49 ` David Aguilar [this message]
2009-08-18 12:42 ` Nicolas Pitre
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=20090818054913.GB37966@gmail.com \
--to=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nico@cam.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).