From: Jonathan Corbet <corbet@lwn.net>
To: Jani Nikula <jani.nikula@linux.intel.com>,
Randy Dunlap <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-doc@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: [PATCH] scripts/get_abi.pl: ignore some temp files
Date: Thu, 04 Jan 2024 08:57:47 -0700 [thread overview]
Message-ID: <87o7e15bwk.fsf@meer.lwn.net> (raw)
In-Reply-To: <871qax6t6k.fsf@meer.lwn.net>
Jonathan Corbet <corbet@lwn.net> writes:
> Jani Nikula <jani.nikula@linux.intel.com> writes:
>
>> On Wed, 03 Jan 2024, Jonathan Corbet <corbet@lwn.net> wrote:
>>> It would have been nice to create all of those files with a .abi
>>> extension so we didn't have to do this kind of blocklisting, but so be
>>> it.
>>
>> Alternatively, we could switch to yaml instead of using another homebrew
>> format with another homebrew parser, and rename them .yaml.
>
> But ... we didn't invent that! :)
>
> That is, of course, a better idea. It would be a good project for
> somebody.
Thinking about this a bit further ... is there anything other than
get_abi.pl that parses these files? If so, that would, of course,
complicate a switch to YAML.
If not, though ... and if we're changing the format ... maybe we should
just turn them into RST and do away with the extra processing step
entirely?
jon
next prev parent reply other threads:[~2024-01-04 15:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-28 23:31 [PATCH] scripts/get_abi.pl: ignore some temp files Randy Dunlap
2024-01-03 21:03 ` Jonathan Corbet
2024-01-03 22:06 ` Randy Dunlap
2024-01-04 11:03 ` Jani Nikula
2024-01-04 14:59 ` Jonathan Corbet
2024-01-04 15:57 ` Jonathan Corbet [this message]
2024-01-04 23:37 ` Mauro Carvalho Chehab
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=87o7e15bwk.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rdunlap@infradead.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).