public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
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,  3 Jan 2014 18:32:02 +0000 (UTC)	[thread overview]
Message-ID: <1388708838.909daf36515b412f1f79f5734e8f82ea3bc10c4e.hwoarang@gentoo> (raw)

commit:     909daf36515b412f1f79f5734e8f82ea3bc10c4e
Author:     David Heidelberger <david.heidelberger <AT> ixit <DOT> cz>
AuthorDate: Fri Jan  3 00:27:18 2014 +0000
Commit:     Markos Chandras <hwoarang <AT> gentoo <DOT> org>
CommitDate: Fri Jan  3 00:27:18 2014 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/devmanual.git;a=commit;h=909daf36

metadata: fix important sequence of email and name in maintainer section

---
 ebuild-writing/misc-files/metadata/text.xml | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/ebuild-writing/misc-files/metadata/text.xml b/ebuild-writing/misc-files/metadata/text.xml
index 675c58c..28c7dfc 100644
--- a/ebuild-writing/misc-files/metadata/text.xml
+++ b/ebuild-writing/misc-files/metadata/text.xml
@@ -144,16 +144,16 @@ A <path>metadata.xml</path> file can contain a number of tags:
   </ti>
 </tr>
 <tr>
-  <ti><brite>&lt;name&gt;</brite></ti>
+  <ti><brite>&lt;email&gt;</brite></ti>
   <ti>
-    The name of an upstream maintainer should contain a block of text with upstream's name.
-    This element is mandatory for an upstream maintainer and must appear only once.
+    The email address of an upstream may appear only once and must appear in first place.
   </ti>
 </tr>
 <tr>
-  <ti><brite>&lt;email&gt;</brite></ti>
+  <ti><brite>&lt;name&gt;</brite></ti>
   <ti>
-    The email address of an upstream may appear only once.
+    The name of an upstream maintainer should contain a block of text with upstream's name.
+    This element is mandatory for an upstream maintainer and must appear only once.
   </ti>
 </tr>
 <tr>
@@ -445,12 +445,12 @@ This example demonstrates the usage of the upstream element:
 <codesample lang="sgml">
 &lt;upstream&gt;
         &lt;maintainer status="inactive"&gt;
-                &lt;name&gt;Foo Bar&lt;/name&gt;
                 &lt;email&gt;foo@bar.bar&lt;/email&gt;
+                &lt;name&gt;Foo Bar&lt;/name&gt;
         &lt;/maintainer&gt;
         &lt;maintainer status="active"&gt;
-                &lt;name&gt;Foo Gentoo&lt;/name&gt;
                 &lt;email&gt;foo@gentoo.org&lt;/email&gt;
+                &lt;name&gt;Foo Gentoo&lt;/name&gt;
         &lt;/maintainer&gt;
         &lt;changelog&gt;http://foo.bar/changelog.txt&lt;/changelog&gt;
         &lt;doc lang="en"&gt;http://foo.bar/doc/index.html&lt;/doc&gt;


             reply	other threads:[~2014-01-03 18:32 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-03 18:32 Markos Chandras [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-06-01 20:39 [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/misc-files/metadata/ Ulrich Müller
2022-05-27  9:04 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
2021-09-11 21:59 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
2020-01-23  7:47 Ulrich Müller
2020-01-14 20:36 Göktürk Yüksek
2017-04-13 19:35 Göktürk Yüksek
2016-12-11  6:19 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-05-18  5:32 Göktürk Yüksek
2016-02-05 12:59 Ulrich Müller
2016-02-05 12:59 Ulrich Müller
2014-01-19 15:14 Markos Chandras
2013-05-12 15:06 Markos Chandras
2012-11-11 19:33 Markos Chandras
2012-11-02 17:49 Markos Chandras

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=1388708838.909daf36515b412f1f79f5734e8f82ea3bc10c4e.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