From: Junio C Hamano <junkio@cox.net>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Move couple of ifdefs after "include config.mk"
Date: Thu, 01 Dec 2005 02:16:56 -0800 [thread overview]
Message-ID: <7v7japjf53.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <81b0412b0512010153t3f768a82m8f9a12effa4a715e@mail.gmail.com> (Alex Riesen's message of "Thu, 1 Dec 2005 10:53:09 +0100")
Alex Riesen <raa.lkml@gmail.com> writes:
> On 12/1/05, Junio C Hamano <junkio@cox.net> wrote:
>> > I have even my specific targets in the config.mak (and would actually
>> > like to have the default target put before including config.mak, so
>> > default call to make is always the same).
Hmph. Do you mean something like this?
-- >8 --
diff --git a/Makefile b/Makefile
index 00521fe..45db357 100644
--- a/Makefile
+++ b/Makefile
@@ -1,3 +1,6 @@
+# The default target of this Makefile is...
+all:
+
# Define MOZILLA_SHA1 environment variable when running make to make use of
# a bundled SHA1 routine coming from Mozilla. It is GPL'd and should be fast
# on non-x86 architectures (e.g. PowerPC), while the OpenSSL version (default
next prev parent reply other threads:[~2005-12-01 10:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 23:23 [PATCH] Move "-include config.mak" to end of configuration section Timo Hirvonen
2005-12-01 0:46 ` Johannes Schindelin
2005-12-01 1:32 ` [PATCH] Move couple of ifdefs after "include config.mk" Timo Hirvonen
2005-12-01 1:43 ` Junio C Hamano
2005-12-01 8:08 ` Johannes Schindelin
2005-12-01 9:04 ` Junio C Hamano
2005-12-01 9:40 ` Alex Riesen
2005-12-01 9:45 ` Junio C Hamano
2005-12-01 9:53 ` Alex Riesen
2005-12-01 10:16 ` Junio C Hamano [this message]
2005-12-01 12:51 ` Alex Riesen
2005-12-03 2:31 ` Johannes Schindelin
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=7v7japjf53.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=raa.lkml@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.