qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: "QEMU Developers" <qemu-devel@nongnu.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH 0/3] target: Rename headers using .def extension to .h.inc
Date: Thu, 27 Oct 2022 17:25:43 +0200	[thread overview]
Message-ID: <57067646-651b-15b1-34a9-99b4d9489421@redhat.com> (raw)
In-Reply-To: <9b3824be-1da3-e5bb-d324-d1f2a417b6e8@linaro.org>

On 27/10/2022 16.12, Philippe Mathieu-Daudé wrote:
> On 27/10/22 08:46, Thomas Huth wrote:
>> On 26/10/2022 01.50, Philippe Mathieu-Daudé wrote:
>>> We use the .h.inc extension to include C headers. To be consistent
>>> with the rest of the codebase, rename the C headers using the .def
>>> extension.
>>>
>>> IDE/tools using our .editorconfig / .gitattributes will leverage
>>> this consistency.
>>
>> Ack for this series, but I've got a meta-question: Does anybody remember 
>> why we are using .h.inc and not .inc.h for such headers? .h.inc has to be 
>> manually configured in most editors for supporting syntax highlighting 
>> here - with .inc.h most editors would get it right by default instead...
> 
> Daniel synthesized the reason here:
> https://lore.kernel.org/qemu-devel/20200817165207.GN4775@redhat.com/
> 
>  >> IIRC, we need to use  c.inc, because Meson has specific semantics
>  >> around a file ending in ".c" that we don't want.
> 
> First explanation from Paolo:
> 
> https://lore.kernel.org/qemu-devel/36032642-9bea-8625-65a6-bd4afc7e459d@redhat.com/ 
> 
> 
> See also for generic .*.inc admitted as convention:
> https://lore.kernel.org/qemu-devel/CAFEAcA-kOs3dKhh3SRchg6Ne8QL8kwyz+2ihDC6ND2v-seuRfw@mail.gmail.com/ 
> 
> Could be worth mentioning in docs/devel/build-system.rst...

Thanks for the summary! ... now if someone (who feels confident about all of 
this) could add some sentences to build-system.rst, that would be really 
great...

  Thomas



  reply	other threads:[~2022-10-27 15:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-25 23:50 [PATCH 0/3] target: Rename headers using .def extension to .h.inc Philippe Mathieu-Daudé
2022-10-25 23:50 ` [PATCH 1/3] target/m68k: Rename qregs.def -> qregs.h.inc Philippe Mathieu-Daudé
2022-10-26  9:54   ` Laurent Vivier
2022-11-02 18:29   ` Laurent Vivier
2022-10-25 23:50 ` [PATCH 2/3] target/s390x: Rename insn-data/format.def -> insn-data/format.h.inc Philippe Mathieu-Daudé
2022-10-27  6:45   ` Thomas Huth
2022-11-02 18:30   ` Laurent Vivier
2022-10-25 23:50 ` [PATCH 3/3] target/tricore: Rename csfr.def -> csfr.h.inc Philippe Mathieu-Daudé
2022-10-26  8:21   ` Bastian Koppelmann
2022-11-02 18:30   ` Laurent Vivier
2022-10-26  9:45 ` [PATCH 0/3] target: Rename headers using .def extension to .h.inc Alex Bennée
     [not found] ` <8d197b71-937a-5693-3b7f-ea4bded8c360@redhat.com>
2022-10-27 14:12   ` Philippe Mathieu-Daudé
2022-10-27 15:25     ` Thomas Huth [this message]
2022-10-27 14:39 ` Markus Armbruster
2022-10-27 15:01   ` Peter Maydell
2022-10-27 17:17     ` Markus Armbruster
2022-10-27 17:24       ` Peter Maydell
2022-10-28  4:37         ` Markus Armbruster

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=57067646-651b-15b1-34a9-99b4d9489421@redhat.com \
    --to=thuth@redhat.com \
    --cc=berrange@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.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 NNTP newsgroup(s).