unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Cc: 51500@debbugs.gnu.org
Subject: [bug#51500] [PATCH] gnu: Add kiwix-tools
Date: Tue, 7 Dec 2021 17:41:22 -0500	[thread overview]
Message-ID: <Ya/jEsbmenEz+6A9@jasmine.lan> (raw)
In-Reply-To: <20211030075156.657aab8f@primarylaptop.localdomain>

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

On Sat, Oct 30, 2021 at 07:51:56AM +0200, Denis 'GNUtoo' Carikli wrote:
> Last time I sent a patch I was told that "by convention we keep [the
> signed-off-by] for the person who applies the patch.".
> 
> Does it means that next times I send patches, it's better if I do not
> add my signed-off-by at all?

Right. In Guix, we used the "signed-off-by" line to say who pushed the
patch on behalf of its author.

This information is actually always there in the Git history, but it's
not shown unless you add '--format=full' to commands such as `git log`
and `git show`.

And of course, the ultimate source of truth about who pushed the patch
is contained in the PGP signature of the commit, shown with a command
such as `git show --show-signature 9e67f2ad418e9a5a7a83`.

So, using "signed-off-by" in this way is just for convenience, for
anyone reading the log. This convention is described in the manual
section Commit Access:

https://guix.gnu.org/manual/en/html_node/Commit-Access.html#Commit-Access

> Or is it better if I leave it and that it get stripped by the person
> who merge the patch each time as through that way way I also formally
> signed the developer certificate of origin, and even if it's stripped
> it offers more guarantees.

You can do as you like, but adding the line "signed-off-by" to your
patches does not communicate anything related to copyright ownership or
licensing.

It's assumed that you are sharing your patches under the license used by
Guix, and that you have the right to do so. If it happens that we accept
a contribution that does not meet those criteria, we will remove it from
Guix, as part of our "Commitment to Correct Mistakes", which is part of
the Free System Distribution Guidelines that we follow:

https://www.gnu.org/distros/free-system-distribution-guidelines.en.html

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2021-12-07 22:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-30  5:36 [bug#51500] [PATCH] gnu: Add kiwix-tools Denis 'GNUtoo' Carikli
2021-10-30  5:51 ` Denis 'GNUtoo' Carikli
2021-12-07 17:14   ` Denis 'GNUtoo' Carikli
2021-12-07 22:41   ` Leo Famulari [this message]
2021-12-07 22:29 ` bug#51500: " Leo Famulari

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=Ya/jEsbmenEz+6A9@jasmine.lan \
    --to=leo@famulari.name \
    --cc=51500@debbugs.gnu.org \
    --cc=GNUtoo@cyberdimension.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.
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).