From: "Markos Chandras" <hwoarang@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/misc-files/metadata/
Date: Fri, 2 Nov 2012 17:49:29 +0000 (UTC) [thread overview]
Message-ID: <1351878532.73fcee4546c673c10c68522359d37c7064a54a3a.hwoarang@gentoo> (raw)
commit: 73fcee4546c673c10c68522359d37c7064a54a3a
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Fri Sep 23 08:54:03 2011 +0000
Commit: Markos Chandras <hwoarang <AT> gentoo <DOT> org>
CommitDate: Fri Nov 2 17:48:52 2012 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/devmanual.git;a=commit;h=73fcee45
Make <herd/> optional, remove 'no-herd'. Bug #384175
---
ebuild-writing/misc-files/metadata/text.xml | 7 +++----
1 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/ebuild-writing/misc-files/metadata/text.xml b/ebuild-writing/misc-files/metadata/text.xml
index aca9a49..1cd4081 100644
--- a/ebuild-writing/misc-files/metadata/text.xml
+++ b/ebuild-writing/misc-files/metadata/text.xml
@@ -45,10 +45,9 @@ example might look like:
</codesample>
<p>
-All new packages <b>must</b> include a <c>metadata.xml</c> file which
-specifies at <e>least</e> a herd. If no herd is suitable, <c>no-herd</c>
-should be used, and at least one maintainer must be listed <d/> however,
-if at all possible, find a herd willing to be listed.
+All new packages <b>must</b> include a <c>metadata.xml</c> file. That file
+should specify at least one herd or one maintainer. It is however recommended,
+if at all possible, to find a herd willing to be listed.
</p>
<p>
next reply other threads:[~2012-11-02 17:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 17:49 Markos Chandras [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-11-11 19:33 [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/misc-files/metadata/ Markos Chandras
2013-05-12 15:06 Markos Chandras
2014-01-03 18:32 Markos Chandras
2014-01-19 15:14 Markos Chandras
2016-02-05 12:59 Ulrich Müller
2016-02-05 12:59 Ulrich Müller
2016-05-18 5:32 Göktürk Yüksek
2016-05-18 5:32 Göktürk Yüksek
2016-05-18 5:32 Göktürk Yüksek
2016-05-18 5:32 Göktürk Yüksek
2016-05-18 5:32 Göktürk Yüksek
2016-12-11 6:19 Göktürk Yüksek
2017-04-13 19:35 Göktürk Yüksek
2020-01-14 20:36 Göktürk Yüksek
2020-01-23 7:47 Ulrich Müller
2020-04-20 8:02 Ulrich Müller
2020-04-20 8:02 Ulrich Müller
2020-04-20 8:02 Ulrich Müller
2021-09-11 21:59 Ulrich Müller
2022-01-12 6:34 Ulrich Müller
2022-01-12 6:34 Ulrich Müller
2022-01-12 6:34 Ulrich Müller
2022-05-27 9:04 Ulrich Müller
2022-06-01 20:39 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=1351878532.73fcee4546c673c10c68522359d37c7064a54a3a.hwoarang@gentoo \
--to=hwoarang@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