unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Jacob Hrbek <kreyren@rixotstudio.cz>
Cc: 53336@debbugs.gnu.org
Subject: [bug#53336] [PATCH] qbittorent: Bump 4.2.5 -> 4.4.0
Date: Wed, 19 Jan 2022 12:43:52 +0100	[thread overview]
Message-ID: <ebfd2aeab5d68c961dfd4e7d0fc05ab54ffc6b06.camel@telenet.be> (raw)
In-Reply-To: <a1c33b21-4c0c-bf9d-90f3-00a8dd05c522@rixotstudio.cz>

[-- Attachment #1: Type: text/plain, Size: 1237 bytes --]

[Please keep debbugs in CC or To]

Jacob Hrbek schreef op wo 19-01-2022 om 09:49 [+0000]:
> I don't have commit access so it's projected to be merged by
> privileged developer on my behalf thus the signed-off-by line so that
> i am not held liable (i am aware that GPLv3 has no liability clause)
> for the changes as GNU Guix lacks sufficient QA for the changes imho.

That's neither what that line means in Guix and neither what it means
in Linux (*) (the project that introduced the original Signed-off-by
IIUC), so I don't see where you got this interpretation about Signed-
off-by and liability from.

(*) See Documentation/process/submitting-patches.rst

In fact, Signed-off-by indicates a measure of ‘approval’ (in Guix
quite a bit more than in Linux IIUC) -- it's not explicitly spelled
out, but Linux' and Guix' contributing documentation seems too imply
this to some degree.

As such, assuming ‘Signed-off-by’ impacts liability somehow,
I would find it more likely that it would increase the chance
of being held liable than decreasing the chance of being held
liable.  Or maybe the inverse holds, who knows, I don't know
how liability and responsibility works legally.

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  parent reply	other threads:[~2022-01-19 12:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-18  3:28 [bug#53336] [PATCH] qbittorent: Bump 4.2.5 -> 4.4.0 Jacob Hrbek
2022-01-19  9:04 ` Maxime Devos
     [not found]   ` <a1c33b21-4c0c-bf9d-90f3-00a8dd05c522@rixotstudio.cz>
2022-01-19 11:43     ` Maxime Devos [this message]
2022-01-19 11:55 ` [bug#53336] [PATCH] qbittorrent: " Jacob Hrbek
2022-01-19 11:56   ` Jacob Hrbek
2022-01-23  9:48     ` Nicolas Goaziou
2022-01-23  9:53 ` [bug#53336] [PATCH] gnu: git-annex: Update to 8.20211231 Jacob Hrbek
2022-01-23 13:04 ` [bug#53336] [PATCH] gnu: qbittorrent: Update to 4.4.0 Jacob Hrbek
2022-01-23 13:05   ` Jacob Hrbek
2022-01-23 16:43   ` bug#53336: " Nicolas Goaziou
2022-01-23 16:44     ` [bug#53336] " Jacob Hrbek

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ebfd2aeab5d68c961dfd4e7d0fc05ab54ffc6b06.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=53336@debbugs.gnu.org \
    --cc=kreyren@rixotstudio.cz \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).