From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-devel@nongnu.org, fam@euphon.net, f4bug@amsat.org,
aurelien@aurel32.net, pbonzini@redhat.com, stefanha@redhat.com,
crosa@redhat.com, "Thomas Huth" <thuth@redhat.com>
Subject: Re: [PATCH v3 06/13] docs/devel: simplify the minimal checklist
Date: Fri, 1 Sep 2023 11:23:07 +0100 [thread overview]
Message-ID: <ZPG7i36+ppw1pbh8@redhat.com> (raw)
In-Reply-To: <87edjip5j1.fsf@linaro.org>
On Fri, Sep 01, 2023 at 11:08:15AM +0100, Alex Bennée wrote:
>
> Philippe Mathieu-Daudé <philmd@linaro.org> writes:
>
> > Ping?
> >
> > On 5/7/23 13:44, Philippe Mathieu-Daudé wrote:
> >> Hi Alex,
> >> On 17/11/22 18:25, Alex Bennée wrote:
> >>> The bullet points are quite long and contain process tips. Move those
> >>> bits of the bullet to the relevant sections and link to them. Use a
> >>> table for nicer formatting of the checklist.
> >>>
> >>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> >>> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
> >>> Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
> >>> Message-Id: <20221111145529.4020801-8-alex.bennee@linaro.org>
> >>> ---
> >>> docs/devel/submitting-a-patch.rst | 75 ++++++++++++++++++++-----------
> >>> 1 file changed, 49 insertions(+), 26 deletions(-)
> >>
> >>> @@ -314,10 +320,12 @@ git repository to fetch the original commit.
> >>> Patch emails must include a ``Signed-off-by:`` line
> >>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >>> -For more information see `SubmittingPatches 1.12
> >>> -<http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/SubmittingPatches?id=f6f94e2ab1b33f0082ac22d71f66385a60d8157f#n297>`__.
> >>> -This is vital or we will not be able to apply your patch! Please use
> >>> -your real name to sign a patch (not an alias or acronym).
> >> Revisiting this patch, asking for some real name instead of alias
> >> was at least helpful during patch review, we could address the
> >> contributor by its name. Addressing an acronym is socially weird
> >> (at least in my culture netiquette).
>
> Is it that weird? We use nicks all the time on IRC.
>
> The only driver for real names for the signoff is its harder to have
> confidence the contribution is valid because you might not be able to
> find who is behind an anonymous nick if something comes up later.
The Signed-off-by is intended as a legal attestation of permission
to contribute. Having the signoff use an obviously anonymous nick
could be said to undermine the legal value of the Signed-off-by.
That's not to say something that /looks/ like a real name is
actually the persons real name - we can't prove that without ID
checks which we're not going to do.
Something that looks like a real name is at least plausible to
accept as a persons' real world identity, where as a nick is
clearly just an online persona where there is an explicit intent
to hide the real identify. This kind of distinction / intent often
matters in the legal arena.
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 :|
next prev parent reply other threads:[~2023-09-01 10:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 17:25 [PATCH for 7.2 v3 00/13] testing and doc updates (pre-PR) Alex Bennée
2022-11-17 17:25 ` [PATCH v3 01/13] Run docker probe only if docker or podman are available Alex Bennée
2022-11-17 17:25 ` [PATCH v3 02/13] tests/avocado/machine_aspeed.py: Reduce noise on the console for SDK tests Alex Bennée
2022-11-17 17:25 ` [PATCH v3 03/13] tests/docker: allow user to override check target Alex Bennée
2022-11-17 17:25 ` [PATCH v3 04/13] docs/devel: add a maintainers section to development process Alex Bennée
2022-11-18 7:49 ` Philippe Mathieu-Daudé
2022-11-22 9:45 ` Alex Bennée
2022-11-17 17:25 ` [PATCH v3 05/13] docs/devel: make language a little less code centric Alex Bennée
2022-11-18 7:52 ` Philippe Mathieu-Daudé
2022-11-17 17:25 ` [PATCH v3 06/13] docs/devel: simplify the minimal checklist Alex Bennée
2022-11-18 7:55 ` Philippe Mathieu-Daudé
2023-07-05 11:44 ` Philippe Mathieu-Daudé
2023-08-25 7:25 ` Philippe Mathieu-Daudé
2023-09-01 10:08 ` Alex Bennée
2023-09-01 10:23 ` Daniel P. Berrangé [this message]
2022-11-17 17:25 ` [PATCH v3 07/13] docs/devel: try and improve the language around patch review Alex Bennée
2022-11-18 7:57 ` Philippe Mathieu-Daudé
2022-11-17 17:25 ` [PATCH v3 08/13] tests/avocado: Raise timeout for boot_linux.py:BootLinuxPPC64.test_pseries_tcg Alex Bennée
2022-11-17 17:25 ` [PATCH v3 09/13] tests/avocado: introduce alpine virt test for CI Alex Bennée
2022-11-18 8:04 ` Philippe Mathieu-Daudé
2022-11-17 17:25 ` [PATCH v3 10/13] tests/avocado: skip aarch64 cloud TCG tests in CI Alex Bennée
2022-11-18 8:05 ` Philippe Mathieu-Daudé
2022-11-17 17:25 ` [PATCH v3 11/13] gitlab: integrate coverage report Alex Bennée
2022-11-17 17:25 ` [PATCH v3 12/13] tests/avocado/boot_linux.py: Bump aarch64 virt test timeout to 720s Alex Bennée
2022-11-18 8:07 ` Philippe Mathieu-Daudé
2022-11-21 21:25 ` Peter Maydell
2022-11-17 17:25 ` [PATCH v3 13/13] ci: replace x86_64 macos-11 with aarch64 macos-12 Alex Bennée
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=ZPG7i36+ppw1pbh8@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=aurelien@aurel32.net \
--cc=crosa@redhat.com \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--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 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).