qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Samuel Tardieu" <sam@rfc1149.net>,
	"Zhao Liu" <zhao1.liu@intel.com>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"Alexander Graf" <agraf@csgraf.de>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Phil Mathieu-Daudé" <philmd@linaro.org>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Thomas Huth" <thuth@redhat.com>, "Kevin Wolf" <kwolf@redhat.com>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
	qemu-devel@nongnu.org
Subject: Re: [PATCH 1/2] docs: introduce dedicated page about code provenance / sign-off
Date: Mon, 29 Jan 2024 11:00:46 +0000	[thread overview]
Message-ID: <ZbeFXkjw4B5Nb6qd@redhat.com> (raw)
In-Reply-To: <CAFEAcA-JMCj2wVRv0JmDmmmLZiMDa1PZ2yU1QUpgiJxnaVQJ_w@mail.gmail.com>

On Mon, Jan 29, 2024 at 10:41:38AM +0000, Peter Maydell wrote:
> On Mon, 29 Jan 2024 at 09:47, Samuel Tardieu <sam@rfc1149.net> wrote:
> > However, this is not what QEMU has been using as far as I can see,
> > as S-o-b tend to stay in their original positions. I even opened
> > an issue on b4 a few weeks ago because of this
> > <https://github.com/mricon/b4/issues/16>, and I reverted to using
> > git-publish. But if this is ok to use an arbitrary order for
> > non-S-o-b headers, I can get back to b4.
> 
> I think QEMU doesn't have a specific existing practice here.
> What you see is largely the result of people using whatever
> tooling they have and accepting the ordering it gives them.
> So I don't think you should stop using b4 just because
> the ordering it happens to produce isn't the same as
> somebody else's tooling.
> 
> I think trying to impose some subtle distinction of meaning
> on the ordering of tags is not going to work, because there
> are going to be too many cases where people don't adhere
> to the ordering distinction because they don't know about
> it or don't understand it.
> 
> As Daniel says, as long as the Signed-off-by tags are
> in basically the right order for developer vs maintainer
> that's the only strong ordering constraint we have.

To think of it another way....

Signed-off-by is the only tag which has defined legal meaning
in terms of asserting that the people involved have permission
to contribute.

All the other tags (Reviewed/Tested/etc) are merely a historical
record of the development process, and have no legal implications.

This makes Signed-off-by the important one, and the others all
in the "nice to have" category.

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2024-01-29 11:01 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-23 11:40 [PATCH 0/2] docs: define policy forbidding use of "AI" / LLM code generators Daniel P. Berrangé
2023-11-23 11:40 ` [PATCH 1/2] docs: introduce dedicated page about code provenance / sign-off Daniel P. Berrangé
2023-11-23 11:58   ` Philippe Mathieu-Daudé
2023-11-23 17:08     ` Daniel P. Berrangé
2023-11-23 23:56       ` Michael S. Tsirkin
2023-11-23 13:01   ` Peter Maydell
2023-11-23 17:12     ` Daniel P. Berrangé
2023-11-23 13:16   ` Kevin Wolf
2023-11-23 17:12     ` Daniel P. Berrangé
2023-11-23 14:25   ` Michael S. Tsirkin
2023-11-23 17:16     ` Daniel P. Berrangé
2023-11-23 17:33       ` Michael S. Tsirkin
2023-11-24 11:11         ` Philippe Mathieu-Daudé
2023-11-24 11:27           ` Michael S. Tsirkin
2023-11-24  9:49       ` Kevin Wolf
2023-11-23 15:13   ` Stefan Hajnoczi
2024-01-27 14:36   ` Zhao Liu
2024-01-29  9:31     ` Daniel P. Berrangé
2024-01-29  9:35       ` Samuel Tardieu
2024-01-29 10:41         ` Peter Maydell
2024-01-29 11:00           ` Daniel P. Berrangé [this message]
2023-11-23 11:40 ` [PATCH 2/2] docs: define policy forbidding use of "AI" / LLM code generators Daniel P. Berrangé
2023-11-23 12:57   ` Alex Bennée
2023-11-23 17:37     ` Michal Suchánek
2023-11-23 23:27       ` Michael S. Tsirkin
2023-11-23 17:46     ` Daniel P. Berrangé
2023-11-23 23:53       ` Michael S. Tsirkin
2023-11-24 10:17         ` Kevin Wolf
2023-11-24 10:33           ` Alex Bennée
2023-11-24 10:42             ` Michael S. Tsirkin
2023-11-24 10:43               ` Peter Maydell
2023-11-24 11:02                 ` Michael S. Tsirkin
2023-11-24 11:37                 ` Daniel P. Berrangé
2023-11-24 11:39                   ` Michael S. Tsirkin
2023-11-24 11:40                     ` Michael S. Tsirkin
2023-11-23 13:20   ` Kevin Wolf
2023-11-23 14:35   ` Michael S. Tsirkin
2023-11-23 14:56     ` Manos Pitsidianakis
2023-11-23 15:13       ` Michael S. Tsirkin
2023-11-23 15:29       ` Philippe Mathieu-Daudé
2023-11-23 17:06         ` Michael S. Tsirkin
2023-11-23 17:29           ` Michal Suchánek
2023-11-23 18:05             ` Michael S. Tsirkin
2023-11-23 15:32       ` Alex Bennée
2023-11-23 18:02       ` Daniel P. Berrangé
2023-11-23 18:10         ` Peter Maydell
2023-11-24 10:25       ` Kevin Wolf
2023-11-24 10:37         ` Michael S. Tsirkin
2023-11-24 10:42         ` Manos Pitsidianakis
2023-11-23 17:58     ` Daniel P. Berrangé
2023-11-23 22:39       ` Michael S. Tsirkin
2023-11-24  9:06         ` Daniel P. Berrangé
2023-11-24  9:27           ` Michael S. Tsirkin
2023-11-24 10:21           ` Alex Bennée
2023-11-24 10:30             ` Michael S. Tsirkin
2023-11-24 11:41             ` Daniel P. Berrangé
2023-11-23 15:22   ` Stefan Hajnoczi

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=ZbeFXkjw4B5Nb6qd@redhat.com \
    --to=berrange@redhat.com \
    --cc=agraf@csgraf.de \
    --cc=alex.bennee@linaro.org \
    --cc=armbru@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=sam@rfc1149.net \
    --cc=stefanha@redhat.com \
    --cc=thuth@redhat.com \
    --cc=zhao1.liu@intel.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 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).