From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] data/glep:glep-0076 commit in: /
Date: Wed, 29 Aug 2018 16:56:07 +0000 (UTC) [thread overview]
Message-ID: <1535561664.77f5047ca5d02030deb65bca3a5937f52f04b250.ulm@gentoo> (raw)
commit: 77f5047ca5d02030deb65bca3a5937f52f04b250
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Wed Aug 29 16:54:24 2018 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed Aug 29 16:54:24 2018 +0000
URL: https://gitweb.gentoo.org/data/glep.git/commit/?id=77f5047c
fixup! glep-0076: Rename the DCO to "Gentoo Certificate of Origin".
glep-0076.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/glep-0076.rst b/glep-0076.rst
index fa8cfe1..515a20d 100644
--- a/glep-0076.rst
+++ b/glep-0076.rst
@@ -131,7 +131,7 @@ that the contribution can be modified and redistributed in accordance
with the project's license.
For commits made using a VCS, the committer shall certify agreement to
-the certificate of origin by adding ``Signed-off-by: Name <e-mail>``
+the Certificate of Origin by adding ``Signed-off-by: Name <e-mail>``
to the commit message as a separate line. Committers must use their
real name, i.e., the name that would appear in an official document
like a passport.
@@ -295,7 +295,7 @@ The new point was deemed necessary to allow committing license files
into the Gentoo repository, since those files usually do not permit
modification. It has been established that adding a clear provision
for this case is better than excluding those commits from compliance
-with the certificate of origin. Debian was facing a similar problem
+with the Certificate of Origin. Debian was facing a similar problem
[#DEBIAN-LICENSE]_.
The update of point (c) was necessary to allow the new clause being
next reply other threads:[~2018-08-29 16:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 16:56 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-08 13:42 [gentoo-commits] data/glep:master commit in: / Ulrich Müller
2018-09-08 13:41 ` [gentoo-commits] data/glep:glep-0076 " Ulrich Müller
2018-09-03 14:48 Ulrich Müller
2018-08-31 15:35 Ulrich Müller
2018-08-29 16:56 Ulrich Müller
2018-08-24 20:15 Ulrich Müller
2018-08-24 20:15 Ulrich Müller
2018-08-24 20:15 Ulrich Müller
2018-08-24 20:15 Ulrich Müller
2018-06-23 21:37 Ulrich Müller
2018-06-23 21:37 Ulrich Müller
2018-06-19 17:31 Ulrich Müller
2018-06-07 19:26 Ulrich Müller
2018-06-07 19:26 Ulrich Müller
2018-06-07 19:26 Ulrich Müller
2018-06-07 19:26 Ulrich Müller
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=1535561664.77f5047ca5d02030deb65bca3a5937f52f04b250.ulm@gentoo \
--to=ulm@gentoo.org \
--cc=gentoo-commits@lists.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