From: Jan Beulich <jbeulich@suse.com>
To: Dmytro Prokopchuk1 <dmytro_prokopchuk1@epam.com>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Anthony PERARD" <anthony.perard@vates.tech>,
"Michal Orzel" <michal.orzel@amd.com>,
"Julien Grall" <julien@xen.org>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] kconfig: remove references to docs/misc/kconfig{,-language}.txt files
Date: Fri, 31 Oct 2025 13:36:00 +0100 [thread overview]
Message-ID: <32623b69-3171-44e6-8fdf-ea67e7838b00@suse.com> (raw)
In-Reply-To: <98fc0e0c-f298-4252-8e7d-f49af56146b6@epam.com>
On 31.10.2025 13:04, Dmytro Prokopchuk1 wrote:
> On 10/29/25 15:57, Jan Beulich wrote:
>> On 29.10.2025 14:38, Dmytro Prokopchuk1 wrote:
>>> These files 'docs/misc/kconfig{,-language}.txt' were deleted, but
>>> references are still present in Xen. Remove them to clean-up.
>>>
>>> Fixes: f80fe2b34f08 ("xen: Update Kconfig to Linux v5.4")
>>
>> Hmm, that commit replaced the .txt files with .rst ones, so maybe you want a
>> 2nd tag here referencing 044503f61c95 ("docs: Delete kconfig docs to fix
>> licensing violation")?
> Well, I saw that commit, but intentionally selected first one.
> Looks like commit 044503f61c95 is more appropriate.
I'd suggest to keep the other one as well.
Jan
prev parent reply other threads:[~2025-10-31 12:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 13:38 [PATCH] kconfig: remove references to docs/misc/kconfig{,-language}.txt files Dmytro Prokopchuk1
2025-10-29 13:57 ` Jan Beulich
2025-10-31 12:04 ` Dmytro Prokopchuk1
2025-10-31 12:36 ` Jan Beulich [this message]
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=32623b69-3171-44e6-8fdf-ea67e7838b00@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=dmytro_prokopchuk1@epam.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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).