1 |
commit: b505dd794cbf9f428f569e9c892c54e580f6a3e7 |
2 |
Author: Sam James <sam <AT> gentoo <DOT> org> |
3 |
AuthorDate: Sun Mar 21 04:29:53 2021 +0000 |
4 |
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org> |
5 |
CommitDate: Tue Mar 30 16:00:52 2021 +0000 |
6 |
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=b505dd79 |
7 |
|
8 |
ebuild-maintenance/git: reference pkgcheck scan --commits and pkgdev |
9 |
|
10 |
Signed-off-by: Sam James <sam <AT> gentoo.org> |
11 |
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org> |
12 |
|
13 |
ebuild-maintenance/git/text.xml | 29 +++++++++++++++-------------- |
14 |
1 file changed, 15 insertions(+), 14 deletions(-) |
15 |
|
16 |
diff --git a/ebuild-maintenance/git/text.xml b/ebuild-maintenance/git/text.xml |
17 |
index 5240f6a..fc2738a 100644 |
18 |
--- a/ebuild-maintenance/git/text.xml |
19 |
+++ b/ebuild-maintenance/git/text.xml |
20 |
@@ -113,10 +113,10 @@ the historical commits after the initial git commit. |
21 |
|
22 |
<p> |
23 |
The recommended way of committing to the Gentoo repository is to use <c>repoman |
24 |
-commit</c>. It automatically performs the necessary QA checks on the package |
25 |
-being committed and has other features helping with the Gentoo workflow. |
26 |
-However, it is currently limited to creating a single commit to a single |
27 |
-package. |
28 |
+commit</c> or <c>pkgdev commit</c> (then <c>pkgdev push</c>). It automatically |
29 |
+performs the necessary QA checks on the package being committed and has other |
30 |
+features helping with the Gentoo workflow. However, <c>repoman</c> is currently |
31 |
+limited to creating a single commit to a single package. |
32 |
</p> |
33 |
|
34 |
<p> |
35 |
@@ -127,17 +127,18 @@ used. The valid uses of git include: |
36 |
<ul> |
37 |
<li>creating commits spanning multiple packages and/or multiple areas |
38 |
of the Gentoo repository (eclasses, licenses, profiles…),</li> |
39 |
-<li>amending a commit created via <c>repoman commit</c> with additional files |
40 |
-or fixups,</li> |
41 |
-<li>combining multiple commits created via <c>repoman commit</c> using <c>git |
42 |
-rebase</c>.</li> |
43 |
+<li>amending a commit created via <c>repoman commit</c> or <c>pkgdev commit</c> |
44 |
+with additional files or fixups,</li> |
45 |
+<li>combining multiple commits created via <c>repoman commit</c> or |
46 |
+<c>pkgdev commit</c> using <c>git rebase</c>.</li> |
47 |
</ul> |
48 |
|
49 |
<p> |
50 |
-Whenever repoman is not used to commit, you need to manually verify all |
51 |
-packages affected by the commit using <c>repoman full</c>. Since repoman |
52 |
-is not aware of staged changes, please make sure that all files are included |
53 |
-in the commit. Also when not using repoman, you must perform a manual sign-off |
54 |
+Whenever <c>repoman</c> or <c>pkgdev</c> is not used to commit, you need to |
55 |
+manually verify all packages affected by the commit using <c>repoman full</c> or |
56 |
+<c>pkgcheck scan --commits</c>. When using <c>repoman</c>, it won't be aware of |
57 |
+staged changes, so ensure that all files are included in the commit. |
58 |
+Also, when using <c>git</c> manually, you must perform a manual sign-off |
59 |
to the <uri link="https://www.gentoo.org/glep/glep-0076.html#certificate-of-origin"> |
60 |
Certificate of Origin</uri> using the <c>-s</c> or <c>--signoff</c> option |
61 |
with your git commit commands. Make sure you have read and understand the |
62 |
@@ -219,8 +220,8 @@ appropriately: |
63 |
</p> |
64 |
|
65 |
<ul> |
66 |
-<li><c>${CATEGORY}/${PN}:</c>Single Package (Note that <c>repoman commit</c> |
67 |
-automatically inserts this for you)</li> |
68 |
+<li><c>${CATEGORY}/${PN}:</c> Single Package (Note that <c>repoman commit</c> |
69 |
+and <c>pkgdev commit</c> will automatically insert this for you)</li> |
70 |
<li><c>${CATEGORY}:</c> Package Category</li> |
71 |
<li><c>profiles:</c> Profile Directory</li> |
72 |
<li><c>${ECLASS}.eclass:</c> Eclass Directotry</li> |