public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Chris Demetriou <cgd@google.com>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [obvious patch] add missing chmod to when copying headers
Date: Fri, 12 Mar 2010 19:52:00 -0000	[thread overview]
Message-ID: <2e7be40c1003121051w6bb3c2f1v96b9e12fd77e134a@mail.gmail.com> (raw)
In-Reply-To: <4B9A1629.20900@gnu.org>

On Fri, Mar 12, 2010 at 02:23, Paolo Bonzini <bonzini@gnu.org> wrote:
>> bootstrapped, verified permissions manually, committed as obvious.
>
> ... but why didn't you use $(INSTALL_DATA)? :-)

*chuckle*  there are actually reasons, believe it or not!  Just
because it's obvious doesn't mean I didn't think about it.  8-)

(a) because the rest of the code here doesn't, and

(b) this *isn't* actually *installing* anything!  it's populating an
include directory internal to the build process.  The actual header
installation happens thanks to the install-headers-* targets AFAICT
(which don't use INSTALL_DATA either 8-).  It's not obvious to me
(esp. in light of the way the rest of the code works) that
INSTALL_DATA is appropriate here.


Changing install-headers-* may be appropriate... but it seems obvious
that a bunch of work was put into its current implementation as-is
(three separate implementations!).  At *minimum* that would be
non-obvious, whereas making all the headers copied in stmp-int-hdrs be
chmodded consistently *is* obvious.  8-)



chris

  reply	other threads:[~2010-03-12 18:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-11 20:31 Chris Demetriou
2010-03-11 21:55 ` Basile Starynkevitch
     [not found]   ` <2e7be40c1003111408g5d8cba66r9605cf12a79bb22c@mail.gmail.com>
2010-03-11 22:14     ` Chris Demetriou
2010-03-12 10:44 ` Paolo Bonzini
2010-03-12 19:52   ` Chris Demetriou [this message]
2010-03-12 20:26     ` Paolo Bonzini
2010-03-15  7:49 ` Eric Botcazou
2010-03-15  8:06   ` Chris Demetriou
2010-03-15  8:57     ` Chris Demetriou
2010-03-15  9:09       ` Eric Botcazou

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=2e7be40c1003121051w6bb3c2f1v96b9e12fd77e134a@mail.gmail.com \
    --to=cgd@google.com \
    --cc=bonzini@gnu.org \
    --cc=gcc-patches@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).