From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: "Michał Górny" <mgorny@gentoo.org>
Subject: [gentoo-dev] [PATCH v2] glep-0066: Update the meaning of Signed-off-by
Date: Tue, 18 Sep 2018 09:50:30 +0200 [thread overview]
Message-ID: <20180918075031.30877-1-mgorny@gentoo.org> (raw)
Reported-by: Michael Orlitzky <mjo@gentoo.org>
---
glep-0066.rst | 25 ++++++++++++++++++-------
1 file changed, 18 insertions(+), 7 deletions(-)
diff --git a/glep-0066.rst b/glep-0066.rst
index a605cf2..a352175 100644
--- a/glep-0066.rst
+++ b/glep-0066.rst
@@ -4,10 +4,10 @@ Title: Gentoo Git Workflow
Author: Michał Górny <mgorny@gentoo.org>
Type: Standards Track
Status: Final
-Version: 1
+Version: 1.1
Created: 2017-07-24
-Last-Modified: 2017-11-13
-Post-History: 2017-07-25, 2017-09-28, 2017-10-11
+Last-Modified: 2018-09-18
+Post-History: 2017-07-25, 2017-09-28, 2017-10-11, 2018-09-18
Content-Type: text/x-rst
---
@@ -18,6 +18,13 @@ with the Gentoo ebuild repository. It covers only Gentoo-specific
policies, and is not meant to be a complete guide.
+Change log
+==========
+v1.1
+ Updated the ``Signed-off-by`` footer tag description to account
+ for newly-approved copyright policy.
+
+
Motivation
==========
Although the main Gentoo repository is using git for two years already,
@@ -188,8 +195,8 @@ A few tags of common use are:
- ``Reported-by: Full Name <email@example.com>``,
- ``Reviewed-by: Full Name <email@example.com>`` — usually indicates
full review,
- - ``Signed-off-by: Full Name <email@example.com>`` — DCO approval (not
- used in Gentoo right now),
+ - ``Signed-off-by: Full Name <email@example.com>`` — GCO/DCO approval
+ (defined by GLEP 76 [#GLEP76]_),
- ``Suggested-by: Full Name <email@example.com>``,
- ``Tested-by: Full Name <email@example.com>``.
@@ -364,8 +371,9 @@ tags collected from various projects (the Linux kernel, X.org). Those
tags can be used interchangeably with plaintext explanation in the body.
The only tag defined by git itself is the ``Signed-off-by`` line,
-that is created by ``git commit -s``. However, Gentoo does not
-currently enforce a DCO consistently, and therefore it is meaningless.
+that is created by ``git commit -s``. While git does not define
+the precise meaning of it, it is commonly used to reference Certificate
+of Origin sign-off.
The tags subject to machine processing are the ``Bug`` and ``Closes``
lines. Both are used by git.gentoo.org to handle Gentoo Bugzilla
@@ -445,6 +453,9 @@ References
.. [#GLEP63] GLEP 63: Gentoo GPG key policies
(https://www.gentoo.org/glep/glep-0063.html)
+.. [#GLEP76] GLEP 76: Copyright policy
+ (https://www.gentoo.org/glep/glep-0076.html)
+
.. [#REPOMAN_PKG_NAME_COMMIT]
(https://gitweb.gentoo.org/proj/portage.git/commit/?id=46dafadff58da0220511f20480b73ad09f913430)
--
2.19.0
reply other threads:[~2018-09-18 7:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180918075031.30877-1-mgorny@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox