From: George Dunlap <george.dunlap@eu.citrix.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH 0/7] tools: remove private Makefile variables
Date: Wed, 6 May 2015 12:49:03 +0100 [thread overview]
Message-ID: <5549FFAF.80501@eu.citrix.com> (raw)
In-Reply-To: <20150506113759.GA8478@aepfle.de>
On 05/06/2015 12:37 PM, Olaf Hering wrote:
> On Wed, May 06, George Dunlap wrote:
>
>> On Fri, Apr 24, 2015 at 11:25 AM, Olaf Hering <olaf@aepfle.de> wrote:
>>> Replace all private variables in Makefiles with automake variables.
>>> This series is based on 92ff75384bce7a11e27fbfaf0c531e88dd1ab4c7.
>>
>> Why?
>
> Why use private variables?
I'm not saying we should use private variables; I'm asking why you think
we shouldn't.
So it sounds like the answer to my question is something like:
"The Xen build system creates a wide range of private variables which
duplicate existing variables created by automake. There's no reason to
duplicate these variables; just use the ones provided by automake. This
makes our code simpler, by not having to duplicate a bunch of
already-defined variables. It also has ${OTHER_POTENTIAL_BENEFIT[@]}."
You should put that explanation in the cover letter, and have some
reference to it in each of the commit messages, so reviewers and
archaeologists understand why you're making this change.
-George
next prev parent reply other threads:[~2015-05-06 11:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 10:25 [PATCH 0/7] tools: remove private Makefile variables Olaf Hering
2015-04-24 10:25 ` [PATCH 1/7] tools: replace private SBINDIR with automake sbindir Olaf Hering
2015-04-24 10:25 ` [PATCH 2/7] tools: replace private BINDIR with automake bindir Olaf Hering
2015-04-24 10:25 ` [PATCH 3/7] tools: replace private PREFIX with automake prefix Olaf Hering
2015-04-24 10:25 ` [PATCH 4/7] tools: replace private INCLUDEDIR with automake includedir Olaf Hering
2015-04-24 10:25 ` [PATCH 5/7] tools: replace private MANDIR with automake mandir Olaf Hering
2015-04-24 10:41 ` Andrew Cooper
2015-04-24 10:25 ` [PATCH 6/7] tools: replace private LIBDIR with automake libdir Olaf Hering
2015-04-24 10:25 ` [PATCH 7/7] tools: replace private DOCDIR with automake docdir Olaf Hering
2015-05-06 11:32 ` [PATCH 0/7] tools: remove private Makefile variables George Dunlap
2015-05-06 11:37 ` Olaf Hering
2015-05-06 11:47 ` Ian Campbell
2015-05-06 11:49 ` George Dunlap [this message]
2015-05-07 8:07 ` Olaf Hering
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=5549FFAF.80501@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=olaf@aepfle.de \
--cc=xen-devel@lists.xen.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 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.