git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	GIT Mailing-list <git@vger.kernel.org>,
	Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: Re: [PATCH 1/1] Makefile: improve SPARSE_FLAGS customisation
Date: Mon, 04 Feb 2019 10:12:42 -0800	[thread overview]
Message-ID: <xmqqwomfv2w5.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <4a8f6b3f-3844-b4e8-2ed2-4078b592dd4b@ramsayjones.plus.com> (Ramsay Jones's message of "Sun, 3 Feb 2019 01:25:22 +0000")

Ramsay Jones <ramsay@ramsayjones.plus.com> writes:

>> Thanks for a detailed and clear explanation here and in the cover
>> letter.  I agree with the motivation and most of the things I see in
>> this patch, but one thing that stands out at me is if we still want
>> to += append to SP_EXTRA_FLAGS in target specific way.  Before this
>> patch, because SPARSE_FLAGS was a dual use variable, it needed +=
>> appending to it in these two places, but that rationale is gone with
>> this patch.
>
> As Luc surmised, in his reply, my intention was that SP_EXTRA_FLAGS
> should be used for any 'internal' settings (not just the target
> specific settings), whereas SPARSE_FLAGS would now be used _only_ for
> user customisation.

OK, if that is the case, then not using "+= append" on SP_EXTRA_FLAGS
and initializing it without allowing environment would be two improvements
that can make the intention more clear, I think.

> Anyway, its late, so I will look at redoing the patches soon.

Thanks.

  reply	other threads:[~2019-02-04 18:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-01 21:03 [PATCH 1/1] Makefile: improve SPARSE_FLAGS customisation Ramsay Jones
2019-02-01 21:46 ` Junio C Hamano
2019-02-01 22:48   ` Luc Van Oostenryck
2019-02-03  1:25   ` Ramsay Jones
2019-02-04 18:12     ` Junio C Hamano [this message]
2019-02-04 19:20       ` Ramsay Jones
2019-02-04 20:15         ` Junio C Hamano
2019-02-04 20:49           ` Ramsay Jones

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=xmqqwomfv2w5.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=luc.vanoostenryck@gmail.com \
    --cc=ramsay@ramsayjones.plus.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).