diff options
author | Ulrich Müller <ulm@gentoo.org> | 2019-12-04 18:06:29 +0100 |
---|---|---|
committer | Ulrich Müller <ulm@gentoo.org> | 2019-12-08 12:32:03 +0100 |
commit | 688b7114682f9faf594d1aa740de1b6dd9c653ac (patch) | |
tree | d0c00f3ebf370bae70d2f9c689857410a7f6d5e3 /ebuild-maintenance | |
parent | Fix nesting of elements. (diff) | |
download | devmanual-688b7114682f9faf594d1aa740de1b6dd9c653ac.tar.gz devmanual-688b7114682f9faf594d1aa740de1b6dd9c653ac.tar.bz2 devmanual-688b7114682f9faf594d1aa740de1b6dd9c653ac.zip |
Elements <brite>, <mail>, and <pkg> are not supported.
Use <c> instead, which seems to be the most appropriate replacement
in their respective contexts.
Signed-off-by: Ulrich Müller <ulm@gentoo.org>
Diffstat (limited to 'ebuild-maintenance')
-rw-r--r-- | ebuild-maintenance/git/text.xml | 2 | ||||
-rw-r--r-- | ebuild-maintenance/maintenance-tasks/text.xml | 16 |
2 files changed, 8 insertions, 10 deletions
diff --git a/ebuild-maintenance/git/text.xml b/ebuild-maintenance/git/text.xml index 70fa46a..ee32c9c 100644 --- a/ebuild-maintenance/git/text.xml +++ b/ebuild-maintenance/git/text.xml @@ -279,7 +279,7 @@ mirrored by Gentoo is referenced, it will be closed (as fixed) automatically with reference to the commit.</li> <li><c>Package-Manager:</c> This is automatically inserted by <c>repoman commit</c> and it specifies the version of -<pkg>sys-apps/portage</pkg> on the system.</li> +<c>sys-apps/portage</c> on the system.</li> <li><c>RepoMan-Options:</c> This is automatically inserted by <c>repoman commit</c> and records the options passed to repoman (such as --force) for the commit.</li> diff --git a/ebuild-maintenance/maintenance-tasks/text.xml b/ebuild-maintenance/maintenance-tasks/text.xml index 2b16ce3..92dd0a0 100644 --- a/ebuild-maintenance/maintenance-tasks/text.xml +++ b/ebuild-maintenance/maintenance-tasks/text.xml @@ -149,18 +149,16 @@ looking for is not listed then please consult the relevant lead. </p> <p> -You should <e>never</e> stabilize packages on -architectures for which you cannot test and instead you should file a bug to -the relevant architecture team, such as <mail link="sparc@gentoo.org"> -sparc@gentoo.org</mail> asking them to stabilize the -ebuild. Alternatively, you may be able to find Gentoo developers on -IRC who could help you with your request. +You should <e>never</e> stabilize packages on architectures for which you +cannot test and instead you should file a bug to the relevant architecture +team, such as <c>sparc@gentoo.org</c> asking them to stabilize the ebuild. +Alternatively, you may be able to find Gentoo developers on IRC who could help +you with your request. </p> <p> -It is best to not use <mail link="arch-maintainers@gentoo.org"> -arch-maintainers@gentoo.org</mail>, adding architecture teams onto a -bug's CC list individually instead. That way teams can remove +It is best to not use <c>arch-maintainers@gentoo.org</c>, adding architecture +teams onto a bug's CC list individually instead. That way teams can remove themselves from the list when they are done, giving a clear indication of which teams still have to stabilize a package. </p> |