From: Junio C Hamano <junkio@cox.net>
To: Yakov Lerner <iler.ml@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Pass -DDEFAULT_GIT_TEMPLATE_DIR only where actually used.
Date: Thu, 22 Jun 2006 00:19:52 -0700 [thread overview]
Message-ID: <7vwtb9veqv.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <0J1800MC1NKJD2C0@mxout2.netvision.net.il> (Yakov Lerner's message of "Thu, 22 Jun 2006 04:47 +0300")
Yakov Lerner <iler.ml@gmail.com> writes:
> Before this patch, -DDEFAULT_GIT_TEMPLATE_DIR was passed on compilation
> command line to all and every %c compiled. In fact the macro
> is used by only one .c file, and unused by all other .c files.
> Remove -DDEFAULT_GIT_TEMPLATE_DIR where unused. Follow the examlpe of
> exec_cmd.o. Pass -DDEFAULT_GIT_TEMPLATE_DIR only where actually used.
Thanks.
By the way, I really started hating that we have $(GIT_VERSION)
in $(TRACK_CFLAGS). Since the version string is tied to the
HEAD commit object name, having it in $(TRACK_CFLAGS) means that
every time I switch branches, make a new commit on top of the
current branch, or checkout-compile-and-then-make-local-change
sequence would force pretty much everything to be rebuilt.
Do you think of any downside if I remove it from the list of
symbols in TRACK_CFLAGS?
For that matter, I do not think tracking prefix_SQ makes much
sense since what matters are bindir, gitexecdir and template_dir
which are already covered, and prefix is merely a convenience to
set these three (four, counting GIT_PYTHON_DIR; we probably
should add it to TRACK_CFLAGS).
Thoughts?
next prev parent reply other threads:[~2006-06-22 7:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 1:47 [PATCH] Pass -DDEFAULT_GIT_TEMPLATE_DIR only where actually used Yakov Lerner
2006-06-22 7:19 ` Junio C Hamano [this message]
2006-06-22 7:49 ` Timo Hirvonen
2006-06-22 9:04 ` Junio C Hamano
2006-06-22 13:12 ` Petr Baudis
2006-06-22 17:11 ` Junio C Hamano
2006-06-22 17:58 ` Petr Baudis
2006-06-22 18:58 ` 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=7vwtb9veqv.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=iler.ml@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox