public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/rbot-gentoo:master commit in: /
Date: Wed, 27 Jan 2016 18:21:50 +0000 (UTC)	[thread overview]
Message-ID: <1453823111.560a65046a8d83fed0e87f577efe5247b5da233f.mgorny@gentoo> (raw)

commit:     560a65046a8d83fed0e87f577efe5247b5da233f
Author:     Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Tue Jan 26 15:35:17 2016 +0000
Commit:     Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Tue Jan 26 15:45:11 2016 +0000
URL:        https://gitweb.gentoo.org/proj/rbot-gentoo.git/commit/?id=560a6504

!meta -v: Support project expansion

 gentoo-data.rb | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/gentoo-data.rb b/gentoo-data.rb
index 49c1211..512422f 100644
--- a/gentoo-data.rb
+++ b/gentoo-data.rb
@@ -116,6 +116,13 @@ class GentooPlugin < Plugin
     return if pkg.nil?
 
     meta_print(m, pkg)
+    pkg['maintainers'].each { |maint|
+      return if maint['type'] != 'project'
+      debug("meta -v calling proj for #{maint['email']}")
+      p = params.clone
+      p[:project] = maint['email']
+      project(m, p)
+    }
     pkg['herds'].each { |h|
       debug("meta -v calling herd for #{h}")
       p = params.clone
@@ -424,7 +431,7 @@ class GentooPlugin < Plugin
     "gentoo" => "Available commands: #{Bold}meta#{Bold}, #{Bold}changelog#{Bold}, #{Bold}devaway#{Bold}, #{Bold}herd#{Bold}, #{Bold}proj#{Bold}, #{Bold}expn#{Bold}, #{Bold}glsa#{Bold}, #{Bold}earch#{Bold}, #{Bold}rdep#{Bold}, #{Bold}ddep#{Bold}, #{Bold}pdep#{Bold}",
     "meta" => [
             "meta #{Bold}[cat/]package#{Bold} : Print metadata for the given package",
-            "meta -v #{Bold}[cat/]package#{Bold} : Print metadata for the given package and the members of the package herds.", 
+            "meta -v #{Bold}[cat/]package#{Bold} : Print metadata for the given package and the members of the maintaining projects.",
             ].join("\n"),
     "changelog" => "changelog #{Bold}[cat/]package#{Bold} : Produce changelog statistics for a given package",
     "devaway" => "devaway #{Bold}devname|list#{Bold} : Print the .away for a developer (if any). Using 'list' shows the developers who are away.",


             reply	other threads:[~2016-01-27 18:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27 18:21 Michał Górny [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-11-22  4:25 [gentoo-commits] proj/rbot-gentoo:master commit in: / Robin H. Johnson
2016-11-22  4:25 Robin H. Johnson
2016-11-22  4:17 Robin H. Johnson
2016-11-22  4:11 Robin H. Johnson
2016-08-13 18:24 Michał Górny
2016-06-15  3:13 Robin H. Johnson
2016-05-31 15:01 Robin H. Johnson
2016-01-27 18:21 Michał Górny
2016-01-27 18:21 Michał Górny
2016-01-27 18:21 Michał Górny
2016-01-27 18:21 Michał Górny
2016-01-27 18:21 Michał Górny
2016-01-12 19:09 Michał Górny
2016-01-12 19:09 Michał Górny
2016-01-12 19:09 Michał Górny
2016-01-11 16:25 Robin H. Johnson
2012-04-01 15:59 Robin H. Johnson
2012-02-20  1:40 Robin H. Johnson
2011-11-17 19:55 Robin H. Johnson

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=1453823111.560a65046a8d83fed0e87f577efe5247b5da233f.mgorny@gentoo \
    --to=mgorny@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