From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/hyper-h2/
Date: Fri, 27 Mar 2020 11:35:24 +0000 (UTC) [thread overview]
Message-ID: <1585308908.a08db6d3ceb195ebad03aaa0aba36eab6a594a9e.mgorny@gentoo> (raw)
commit: a08db6d3ceb195ebad03aaa0aba36eab6a594a9e
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Fri Mar 27 11:20:46 2020 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Fri Mar 27 11:35:08 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a08db6d3
dev-python/hyper-h2: Mark ALLARCHES
Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>
dev-python/hyper-h2/metadata.xml | 1 +
1 file changed, 1 insertion(+)
diff --git a/dev-python/hyper-h2/metadata.xml b/dev-python/hyper-h2/metadata.xml
index 658230635a9..652a156f7e5 100644
--- a/dev-python/hyper-h2/metadata.xml
+++ b/dev-python/hyper-h2/metadata.xml
@@ -5,6 +5,7 @@
<email>python@gentoo.org</email>
<name>Python</name>
</maintainer>
+ <stabilize-allarches/>
<upstream>
<maintainer>
<email>cory@lukasa.co.uk</email>
next reply other threads:[~2020-03-27 11:35 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 11:35 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-06 7:16 [gentoo-commits] repo/gentoo:master commit in: dev-python/hyper-h2/ Michał Górny
2020-10-02 20:41 Sam James
2020-10-01 23:06 Sergei Trofimovich
2020-10-01 22:55 Sergei Trofimovich
2020-10-01 22:33 Sergei Trofimovich
2020-09-28 13:53 Göktürk Yüksek
2020-09-20 6:28 Michał Górny
2020-08-04 12:01 Michał Górny
2020-05-27 7:52 Michał Górny
2020-05-04 11:07 Michał Górny
2020-03-27 11:35 Michał Górny
2020-02-18 8:59 Sergei Trofimovich
2020-02-13 13:03 Agostino Sarubbo
2020-02-11 11:30 Agostino Sarubbo
2020-02-11 10:58 Agostino Sarubbo
2020-02-11 10:55 Agostino Sarubbo
2020-02-11 9:52 Agostino Sarubbo
2020-02-11 9:43 Agostino Sarubbo
2020-02-11 8:36 Agostino Sarubbo
2020-02-10 10:54 Michał Górny
2020-02-10 10:54 Michał Górny
2019-12-02 2:48 Aaron Bauman
2019-11-21 21:25 Michał Górny
2019-01-17 20:45 Mikle Kolyada
2018-12-31 10:21 Mikle Kolyada
2018-08-20 18:17 Sergei Trofimovich
2018-07-16 19:57 Michał Górny
2018-07-15 8:37 Michał Górny
2018-05-04 15:17 Mart Raudsepp
2018-04-06 5:23 Matt Turner
2018-03-30 18:08 Sergei Trofimovich
2018-03-18 19:19 Michał Górny
2018-02-22 17:02 Michał Górny
2018-01-04 20:35 Michał Górny
2017-12-13 22:15 Sergei Trofimovich
2017-10-28 22:34 Sergei Trofimovich
2017-09-28 13:42 Michael Palimaka
2017-07-02 15:02 Sergei Trofimovich
2017-07-02 15:02 Sergei Trofimovich
2017-06-28 13:19 Agostino Sarubbo
2017-06-26 20:18 Tobias Klausmann
2017-06-14 17:00 Brian Dolbec
2017-06-14 16:44 Brian Dolbec
2017-06-10 13:17 Brian Dolbec
2017-06-09 18:18 Brian Dolbec
2017-05-26 10:16 Tobias Klausmann
2017-05-03 9:26 Michał Górny
2017-03-29 1:43 Brian Dolbec
2017-03-22 19:48 Markus Meier
2017-03-12 12:30 Anthony G. Basile
2017-02-19 8:40 Markus Meier
2017-02-12 22:20 Zac Medico
2017-01-25 6:39 Jeroen Roovers
2016-12-25 12:42 Manuel Rüger
2016-12-24 21:54 Brian Dolbec
2016-10-28 1:27 Brian Dolbec
2016-10-24 23:17 Brian Dolbec
2016-10-22 1:26 Brian Dolbec
2016-10-07 18:11 Brian Dolbec
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=1585308908.a08db6d3ceb195ebad03aaa0aba36eab6a594a9e.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