From: Markus Armbruster <armbru@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Warner Losh" <imp@bsdimp.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org, "Thomas Huth" <thuth@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Mauro Carvalho Chehab" <mchehab+huawei@kernel.org>,
"Joe Perches" <joe@perches.com>, "John Snow" <jsnow@redhat.com>
Subject: Re: [RFC PATCH v2 08/16] MAINTAINERS: be realistic about *-user
Date: Tue, 03 Feb 2026 11:58:10 +0100 [thread overview]
Message-ID: <871pj23xh9.fsf@pond.sub.org> (raw)
In-Reply-To: <aYHDKafOxzPL8DhL@redhat.com> ("Daniel P. Berrangé"'s message of "Tue, 3 Feb 2026 09:43:05 +0000")
Daniel P. Berrangé <berrange@redhat.com> writes:
> On Mon, Feb 02, 2026 at 02:57:57PM -0700, Warner Losh wrote:
[...]
>> One question I have, should include these lines
>> 🤖 Generated with [Claude Code](https://claude.com/claude-code)
>> Co-Authored-By: Claude <noreply@anthropic.com>
>
> Commit message tags like this are considered to be referring to the
> code in the commit body, so that would be potentially misleading.
>
> Personally, I also don't like the concept of providing free advertizing
> for commercial tools in commit messages.
>
> If you've exclusively used it for commit metadata, then IMHO it would
> be sufficient to just mention this in the cover letter description,
> and explicitly say it had no part in writing the code, etc.
+1
next prev parent reply other threads:[~2026-02-03 10:59 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 14:57 [RFC PATCH v2 00/16] MAINTAINER updates plus conversion of get_maintainers.pl to python Alex Bennée
2026-01-23 14:57 ` [RFC PATCH v2 01/16] MAINTAINERS: fix missing names Alex Bennée
2026-01-26 18:56 ` Pierrick Bouvier
2026-01-23 14:57 ` [RFC PATCH v2 02/16] MAINTAINERS: fix libvirt entry Alex Bennée
2026-01-23 14:57 ` [RFC PATCH v2 03/16] MAINTAINERS: regularise the status fields Alex Bennée
2026-01-23 14:57 ` [RFC PATCH v2 04/16] MAINTAINERS: remove myself as reviewer Alex Bennée
2026-01-26 18:56 ` Pierrick Bouvier
2026-01-23 14:57 ` [RFC PATCH v2 05/16] MAINTAINERS: add maintainer for docs/ Alex Bennée
2026-01-26 18:42 ` Philippe Mathieu-Daudé
2026-01-23 14:57 ` [RFC PATCH v2 06/16] MAINTAINERS: update Arm to Supported status Alex Bennée
2026-01-26 18:43 ` Philippe Mathieu-Daudé
2026-01-23 14:57 ` [RFC PATCH v2 07/16] MAINTAINERS: add reviewer for linux-user Alex Bennée
2026-01-26 18:43 ` Philippe Mathieu-Daudé
2026-01-23 14:57 ` [RFC PATCH v2 08/16] MAINTAINERS: be realistic about *-user Alex Bennée
2026-01-23 15:12 ` Warner Losh
2026-01-23 16:15 ` Alex Bennée
2026-01-23 22:09 ` Warner Losh
2026-01-26 14:37 ` Konstantin Ryabitsev
2026-01-23 16:57 ` Daniel P. Berrangé
2026-01-23 22:14 ` Warner Losh
2026-02-02 21:57 ` Warner Losh
2026-02-03 0:49 ` Warner Losh
2026-02-03 9:53 ` Daniel P. Berrangé
2026-02-03 9:43 ` Daniel P. Berrangé
2026-02-03 10:58 ` Markus Armbruster [this message]
2026-01-23 14:57 ` [RFC PATCH v2 09/16] scripts/get_maintainer.py: minimal argument parsing Alex Bennée
2026-01-23 14:57 ` [RFC PATCH v2 10/16] scripts/get_maintainer.py: resolve the source path Alex Bennée
2026-01-23 14:57 ` [RFC PATCH v2 11/16] scripts/get_maintainer.py: initial parsing of MAINTAINERS Alex Bennée
2026-01-23 14:57 ` [RFC PATCH v2 12/16] scripts/get_maintainer.py: add support for -f Alex Bennée
2026-01-23 14:57 ` [RFC PATCH v2 13/16] scripts/get_maintainer.py: add support reading patch files Alex Bennée
2026-01-23 14:57 ` [RFC PATCH v2 14/16] scripts/get_maintainer.py: add keyword (K:) support Alex Bennée
2026-01-23 14:57 ` [RFC PATCH v2 15/16] scripts/get_maintainer.py: implement basic git fallback support Alex Bennée
2026-01-23 14:57 ` [RFC PATCH v2 16/16] gitlab: add a check-maintainers task Alex Bennée
2026-01-23 15:42 ` [RFC PATCH v2 00/16] MAINTAINER updates plus conversion of get_maintainers.pl to python Pierrick Bouvier
2026-01-23 16:18 ` Alex Bennée
2026-01-23 18:04 ` Pierrick Bouvier
2026-01-23 17:54 ` Joe Perches
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=871pj23xh9.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=imp@bsdimp.com \
--cc=joe@perches.com \
--cc=jsnow@redhat.com \
--cc=mchehab+huawei@kernel.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.