public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jeroen Roovers (jer)" <jer@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
Date: Wed,  3 Aug 2011 19:57:00 +0000 (UTC)	[thread overview]
Message-ID: <20110803195700.D66832004C@flycatcher.gentoo.org> (raw)

jer         11/08/03 19:57:00

  Modified:             index.xml
  Log:
  Remove ambiguity about metadata.xml listings and how to order them, thanks to _AxS_ and few.

Revision  Changes    Path
1.21                 xml/htdocs/proj/en/qa/bug-wranglers/index.xml

file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.21&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.21&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.20&r2=1.21

Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- index.xml	23 Jan 2011 18:43:03 -0000	1.20
+++ index.xml	3 Aug 2011 19:57:00 -0000	1.21
@@ -175,10 +175,11 @@
 less up to date) and read the <c>metadata.xml</c> file you find there. When
 <c>metadata.xml</c> lists a single maintainer or herd, then you assign the bug
 to that maintainer or herd. When the file lists multiple entries, then you
-assign the bug to the first maintainer, and CC the other maintainer(s) and
-herd(s). If you find that <c>metadata.xml</c> lists inappropriate and/or
-confusing contact information, then make a note of that in a comment on the bug
-report and assign/CC the bug report as optimal as possible.
+assign the bug to the first &lt;maintainer&gt;, and CC the other
+&lt;maintainer&gt;(s) and &lt;herd&gt;(s). If you find that <c>metadata.xml</c>
+lists inappropriate and/or confusing contact information, then make a note of
+that in a comment on the bug report and assign/CC the bug report as best as
+possible.
 </li>
 <li>
 In cases where <c>metadata.xml</c> lists a herd which Gentoo Bugzilla






             reply	other threads:[~2011-08-03 19:57 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-03 19:57 Jeroen Roovers (jer) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-12-10 13:45 [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml Lars Wendler (polynomial-c)
2013-08-11 15:29 Jeroen Roovers (jer)
2013-08-11 15:17 Jeroen Roovers (jer)
2013-08-11 14:59 Jeroen Roovers (jer)
2013-08-07 14:44 Jeroen Roovers (jer)
2013-08-07 14:35 Jeroen Roovers (jer)
2012-12-19  3:06 Jeroen Roovers (jer)
2012-05-30 14:28 Jeroen Roovers (jer)
2012-05-18  4:30 Mike Gilbert (floppym)
2011-10-10 19:02 Mike Gilbert (floppym)
2011-09-09  6:20 Justin Lecher (jlec)
2011-08-03 19:57 Jeroen Roovers (jer)
2011-01-23 18:43 Jeroen Roovers (jer)
2010-11-16 15:10 PaweA Hajdan (phajdan.jr)
2010-10-26 18:46 Jeroen Roovers (jer)
2010-10-26 18:35 Jeroen Roovers (jer)
2010-10-03 19:39 Markos Chandras (hwoarang)
2010-05-26  3:36 Jeroen Roovers (jer)
2009-11-09 13:41 Markos Chandras (hwoarang)
2009-10-28 21:27 Jeremy Olexa (darkside)
2009-10-23 18:31 Jeremy Olexa (darkside)
2009-09-29 20:02 Jeremy Olexa (darkside)
2009-03-27 21:37 Jeroen Roovers (jer)
2008-09-10  5:07 Jeroen Roovers (jer)
2008-09-08 16:24 Jeroen Roovers (jer)
2008-09-02 20:35 Jeroen Roovers (jer)
2008-08-21  0:51 Mark Loeser (halcy0n)
2008-07-23 16:19 Jeroen Roovers (jer)
2008-07-23 16:18 Jeroen Roovers (jer)
2008-07-14 19:30 Jeroen Roovers (jer)
2008-07-05  7:40 Christian Faulhammer (opfer)
2008-07-05  3:40 Mark Loeser (halcy0n)

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=20110803195700.D66832004C@flycatcher.gentoo.org \
    --to=jer@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