On Thu, Apr 25, 2024 at 11:34:46AM +0200, Markus Armbruster wrote:
> I just realized I dropped this on the floor. I apologize for the delay.
>
> Daniel P. Berrangé writes:
>
> > On Mon, Jan 08, 2024 at 06:23:37PM +, Daniel P. Berrangé wrote:
> >> The general expectation is that header files
Markus Armbruster writes:
> I just realized I dropped this on the floor. I apologize for the delay.
>
> Daniel P. Berrangé writes:
>
>> On Mon, Jan 08, 2024 at 06:23:37PM +, Daniel P. Berrangé wrote:
>>> The general expectation is that header files should follow the same
>>> file/path namin
I just realized I dropped this on the floor. I apologize for the delay.
Daniel P. Berrangé writes:
> On Mon, Jan 08, 2024 at 06:23:37PM +, Daniel P. Berrangé wrote:
>> The general expectation is that header files should follow the same
>> file/path naming scheme as the corresponding source
On Mon, Jan 08, 2024 at 06:46:38PM +, Daniel P. Berrangé wrote:
> Date: Mon, 8 Jan 2024 18:46:38 +
> From: "Daniel P. Berrangé"
> Subject: Re: [PATCH 01/29] include: move include/qapi/qmp/ to
> include/qobject/
>
> On Mon, Jan 08, 2024 at 06:23:37PM +00
On Mon, Jan 08, 2024 at 06:23:37PM +, Daniel P. Berrangé wrote:
> The general expectation is that header files should follow the same
> file/path naming scheme as the corresponding source file. There are
> various historical exceptions to this practice in QEMU, with one of
> the most notable be
The general expectation is that header files should follow the same
file/path naming scheme as the corresponding source file. There are
various historical exceptions to this practice in QEMU, with one of
the most notable being the include/qapi/qmp/ directory. Most of the
headers there correspond to
