| 1 |
From: Gokturk Yuksek <gokturk@××××××××××.edu> |
| 2 |
|
| 3 |
Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=558642 |
| 4 |
Signed-off-by: Gokturk Yuksek <gokturk@××××××××××.edu> |
| 5 |
--- |
| 6 |
ebuild-writing/user-submitted/text.xml | 4 ++++ |
| 7 |
1 file changed, 4 insertions(+) |
| 8 |
|
| 9 |
diff --git a/ebuild-writing/user-submitted/text.xml b/ebuild-writing/user-submitted/text.xml |
| 10 |
index a148042..68c88f0 100644 |
| 11 |
--- a/ebuild-writing/user-submitted/text.xml |
| 12 |
+++ b/ebuild-writing/user-submitted/text.xml |
| 13 |
@@ -22,6 +22,10 @@ The user-submitted ebuild must not contain custom headers like this: |
| 14 |
|
| 15 |
<p> |
| 16 |
Such information should be included in the git commit message instead. |
| 17 |
+The use of tags such as <c>Suggested-By:</c> or <c>Reported-By:</c>in |
| 18 |
+the commit message, as explained in the |
| 19 |
+<uri link="::ebuild-maintenance#git-commit-message-format">commit |
| 20 |
+message format section</uri>, is highly encouraged. |
| 21 |
Note that ebuilds received in the form of git patches or pull requests |
| 22 |
will have the user as the commit author by default, in which case |
| 23 |
including the user information in the commit message explicitly |
| 24 |
-- |
| 25 |
2.4.10 |
Archives