From: "Göktürk Yüksek" <gokturk@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: ebuild-maintenance/git/
Date: Tue, 29 Oct 2019 20:49:21 +0000 (UTC) [thread overview]
Message-ID: <1572381021.fdc4594387073ec16b6021b1a858fffd5855d18a.gokturk@gentoo> (raw)
commit: fdc4594387073ec16b6021b1a858fffd5855d18a
Author: Wim Muskee <wimmuskee <AT> gmail <DOT> com>
AuthorDate: Wed Oct 23 19:19:10 2019 +0000
Commit: Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
CommitDate: Tue Oct 29 20:30:21 2019 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=fdc45943
ebuild-maintenance/git: add sign-off for Certificate of Origin
Bug: https://bugs.gentoo.org/668686
Closes: https://github.com/gentoo/devmanual.gentoo.org/pull/113
Acked-by: Michał Górny <mgorny <AT> gentoo.org>
Signed-off-by: Wim Muskee <wimmuskee <AT> gmail.com>
Signed-off-by: Göktürk Yüksek <gokturk <AT> gentoo.org>
ebuild-maintenance/git/text.xml | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/ebuild-maintenance/git/text.xml b/ebuild-maintenance/git/text.xml
index c61589d..fb09de7 100644
--- a/ebuild-maintenance/git/text.xml
+++ b/ebuild-maintenance/git/text.xml
@@ -141,7 +141,11 @@ rebase</c>.</li>
Whenever repoman is not used to commit, you need to manually verify all
packages affected by the commit using <c>repoman full</c>. Since repoman
is not aware of staged changes, please make sure that all files are included
-in the commit.
+in the commit. Also when not using repoman, you must perform a manual sign-off
+to the <uri link="https://www.gentoo.org/glep/glep-0076.html#certificate-of-origin">
+Certificate of Origin</uri> using the <c>-s</c> or <c>--signoff</c> option
+with your git commit commands. Make sure you have read and understand the
+actual Certificate.
</p>
</body>
@@ -205,8 +209,9 @@ line. From the third line onward should be a detailed, multiline
explanation of the changes introduced by the commit. At the very end,
auxiliary information such as the bugs related to the commit,
contributors, and reviewers should be listed using RFC822/git style
-tags. The length of the lines in the message should be 70-75
-characters at maximum.
+tags. The sign-off agreement will be added there as well when applied
+with the commit action. The length of the lines in the message should
+be 70-75 characters at maximum.
</p>
<p>
@@ -310,6 +315,7 @@ new bar functionality introduced with this version.
Bug: https://bugs.gentoo.org/00000
Closes: https://bugs.gentoo.org/00001
+Signed-off-by: Alice Bar <a.bar@example.org>
</pre>
</body>
next reply other threads:[~2019-10-29 20:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 20:49 Göktürk Yüksek [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-07 9:39 [gentoo-commits] proj/devmanual:master commit in: ebuild-maintenance/git/ Ulrich Müller
2024-04-13 19:42 Ulrich Müller
2022-11-22 4:17 Sam James
2021-09-27 10:20 Ulrich Müller
2021-03-30 16:10 Ulrich Müller
2021-03-30 16:10 Ulrich Müller
2021-02-23 8:29 Ulrich Müller
2020-01-14 20:36 Göktürk Yüksek
2018-01-03 4:51 Göktürk Yüksek
2018-01-03 4:51 Göktürk Yüksek
2018-01-03 4:51 Göktürk Yüksek
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=1572381021.fdc4594387073ec16b6021b1a858fffd5855d18a.gokturk@gentoo \
--to=gokturk@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