public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Pacho Ramos" <pacho@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: www-apache/modsecurity-crs/
Date: Sun,  7 Aug 2016 09:30:34 +0000 (UTC)	[thread overview]
Message-ID: <1470562188.693e72616951cdf5cc99a646455471bb32309142.pacho@gentoo> (raw)

commit:     693e72616951cdf5cc99a646455471bb32309142
Author:     Pacho Ramos <pacho <AT> gentoo <DOT> org>
AuthorDate: Sun Aug  7 09:20:19 2016 +0000
Commit:     Pacho Ramos <pacho <AT> gentoo <DOT> org>
CommitDate: Sun Aug  7 09:29:48 2016 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=693e7261

www-apache/modsecurity-crs: Cleanup per bug #85210

Package-Manager: portage-2.3.0

 www-apache/modsecurity-crs/metadata.xml | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/www-apache/modsecurity-crs/metadata.xml b/www-apache/modsecurity-crs/metadata.xml
index a47f42a..f73da4e 100644
--- a/www-apache/modsecurity-crs/metadata.xml
+++ b/www-apache/modsecurity-crs/metadata.xml
@@ -1,10 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
 <pkgmetadata>
-  <maintainer type="person">
-    <email>flameeyes@gentoo.org</email>
-    <name>Diego E. Pettenò</name>
-  </maintainer>
   <upstream>
     <remote-id type="github">SpiderLabs/owasp-modsecurity-crs</remote-id>
   </upstream>


             reply	other threads:[~2016-08-07  9:30 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-07  9:30 Pacho Ramos [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-11-03 21:46 [gentoo-commits] repo/gentoo:master commit in: www-apache/modsecurity-crs/ Diego Elio Pettenò
2018-03-29 19:23 Michał Górny
2018-05-20 23:26 Aaron Bauman
2018-10-20 18:01 Mikle Kolyada
2018-10-26  0:52 Thomas Deutschmann
2019-03-04  1:35 Thomas Deutschmann
2020-10-07 18:58 Sam James
2020-10-09  8:41 Agostino Sarubbo
2020-10-09 15:23 Agostino Sarubbo
2020-12-29  2:00 Sam James
2021-12-21  2:05 Sam James
2021-12-22  0:44 Sam James
2021-12-22  0:45 Sam James
2021-12-24  8:02 Sam James
2022-11-21  9:22 Joonas Niilola
2022-11-21  9:22 Joonas Niilola
2022-12-02  3:34 Sam James
2022-12-02  3:38 Sam James
2022-12-02  6:15 John Helmert III
2023-10-28  7:07 Hans de Graaff
2023-10-30 23:13 Sam James
2023-10-31  0:06 Sam James
2024-01-11 14:06 Joonas Niilola
2024-01-11 14:06 Joonas Niilola
2024-03-16  9:26 Joonas Niilola
2024-04-26 17:16 Sam James
2024-04-26 17:16 Sam James
2024-04-27 13:21 Petr Vaněk
2024-04-27 13:21 Petr Vaněk
2024-07-20  6:42 Joonas Niilola
2024-07-20  6:42 Joonas Niilola
2024-10-25 11:36 Joonas Niilola
2024-10-25 11:36 Joonas Niilola
2024-10-26  3:49 Sam James
2024-10-26  3:49 Sam James
2024-10-26  6:02 Joonas Niilola
2024-10-26  6:02 Joonas Niilola
2024-12-04 18:10 Joonas Niilola
2024-12-04 18:10 Joonas Niilola
2024-12-04 18:10 Joonas Niilola
2025-02-11  9:21 Sam James
2025-02-11  9:21 Sam James
2025-02-11  9:49 Sam James
2025-02-11  9:49 Sam James
2025-03-01  9:00 Petr Vaněk
2025-03-01  9:00 Petr Vaněk
2025-03-12 12:38 Petr Vaněk
2025-04-26  1:17 Sam James
2025-04-26  1:25 Sam James

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=1470562188.693e72616951cdf5cc99a646455471bb32309142.pacho@gentoo \
    --to=pacho@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