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] repo/gentoo:master commit in: dev-python/feedparser/
Date: Fri, 16 Oct 2020 12:00:21 +0000 (UTC)	[thread overview]
Message-ID: <1602849611.c8f17758c2cd949e8c0c84fe75301cb147c862d1.mgorny@gentoo> (raw)

commit:     c8f17758c2cd949e8c0c84fe75301cb147c862d1
Author:     Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Fri Oct 16 11:49:42 2020 +0000
Commit:     Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Fri Oct 16 12:00:11 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c8f17758

dev-python/feedparser: Mark ALLARCHES

Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>

 dev-python/feedparser/metadata.xml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/dev-python/feedparser/metadata.xml b/dev-python/feedparser/metadata.xml
index 723c95fec11..dfe7003bfe1 100644
--- a/dev-python/feedparser/metadata.xml
+++ b/dev-python/feedparser/metadata.xml
@@ -5,6 +5,7 @@
     <email>python@gentoo.org</email>
     <name>Python</name>
   </maintainer>
+  <stabilize-allarches/>
   <upstream>
     <remote-id type="google-code">feedparser</remote-id>
     <remote-id type="github">kurtmckee/feedparser</remote-id>


             reply	other threads:[~2020-10-16 12:00 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-16 12:00 Michał Górny [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-30 14:40 [gentoo-commits] repo/gentoo:master commit in: dev-python/feedparser/ Michał Górny
2023-12-11  4:14 Michał Górny
2023-06-09 18:13 Arthur Zamarin
2022-06-21 18:32 Arthur Zamarin
2022-06-21 18:30 Arthur Zamarin
2022-05-22  5:53 Michał Górny
2022-05-20  8:29 Michał Górny
2021-11-11  9:24 Arthur Zamarin
2021-10-09  9:32 Arthur Zamarin
2021-07-25  8:58 Michał Górny
2021-07-25  8:52 Agostino Sarubbo
2021-06-22 16:29 Michał Górny
2021-06-22  5:54 Michał Górny
2021-06-15 21:32 Michał Górny
2021-06-14 21:03 Michał Górny
2021-06-14  6:51 Michał Górny
2021-06-13  6:10 Michał Górny
2021-02-27 21:30 Michał Górny
2021-02-27 12:31 Sam James
2020-12-15  6:34 Sam James
2020-12-15  6:28 Sam James
2020-12-13 21:45 Thomas Deutschmann
2020-12-08 20:17 Sebastian Pipping
2020-11-26  8:26 Michał Górny
2020-11-26  6:56 Agostino Sarubbo
2020-10-25 20:40 Michał Górny
2020-10-18 19:19 Sam James
2020-10-18 19:10 Thomas Deutschmann
2020-09-18 14:41 Michał Górny
2020-09-15 22:19 Michał Górny
2020-09-13  8:44 Sergei Trofimovich
2020-09-13  7:31 Michał Górny
2020-09-10 19:07 Sergei Trofimovich
2020-09-09 21:59 Sergei Trofimovich
2020-09-09 21:35 Sergei Trofimovich
2020-09-09  0:34 Sam James
2020-08-06 15:42 Michał Górny
2020-06-12 15:40 Michał Górny
2020-03-10 18:32 Michał Górny
2020-03-10 18:32 Michał Górny
2019-06-24 20:57 Zac Medico
2019-04-23 15:58 Alexey Shvetsov
2018-06-09 19:42 Mikle Kolyada
2017-10-08 16:24 Tim Harder
2017-05-04 17:16 Manuel Rüger
2017-02-20 18:14 Markus Meier
2017-01-25  9:05 Tobias Klausmann
2017-01-23  6:11 Jeroen Roovers
2017-01-22 16:27 Agostino Sarubbo
2017-01-21 20:33 Agostino Sarubbo
2017-01-18 11:57 Agostino Sarubbo
2017-01-17 16:22 Agostino Sarubbo
2016-11-24  3:28 Mike Gilbert

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=1602849611.c8f17758c2cd949e8c0c84fe75301cb147c862d1.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