From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/soupsieve/
Date: Sat, 11 Jul 2020 08:57:36 +0000 (UTC) [thread overview]
Message-ID: <1594457851.e22e72d3e8f910320b723eacca99616e0f5e85d1.mgorny@gentoo> (raw)
commit: e22e72d3e8f910320b723eacca99616e0f5e85d1
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Sat Jul 11 08:50:37 2020 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Sat Jul 11 08:57:31 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e22e72d3
dev-python/soupsieve: Mark ALLARCHES
Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>
dev-python/soupsieve/metadata.xml | 1 +
1 file changed, 1 insertion(+)
diff --git a/dev-python/soupsieve/metadata.xml b/dev-python/soupsieve/metadata.xml
index de74db44b00..d601a051737 100644
--- a/dev-python/soupsieve/metadata.xml
+++ b/dev-python/soupsieve/metadata.xml
@@ -5,6 +5,7 @@
<email>python@gentoo.org</email>
<name>Python</name>
</maintainer>
+ <stabilize-allarches/>
<upstream>
<remote-id type="pypi">soupsieve</remote-id>
<remote-id type="github">facelessuser/soupsieve</remote-id>
next reply other threads:[~2020-07-11 8:57 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-11 8:57 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-31 9:21 [gentoo-commits] repo/gentoo:master commit in: dev-python/soupsieve/ Michał Górny
2024-08-31 7:51 Jakov Smolić
2024-08-14 6:05 Michał Górny
2024-05-09 19:13 Michał Górny
2023-10-06 15:08 Michał Górny
2023-10-06 14:29 Sam James
2023-09-02 14:11 Michał Górny
2023-05-26 16:55 Michał Górny
2023-05-23 16:08 Michał Górny
2023-05-23 15:44 Arthur Zamarin
2023-04-17 5:26 Michał Górny
2023-03-17 15:58 Michał Górny
2023-03-17 15:53 Sam James
2023-02-15 7:16 Michał Górny
2023-02-13 3:22 Matt Turner
2022-07-10 18:50 Michał Górny
2022-07-10 16:56 Sam James
2022-06-05 16:48 Michał Górny
2022-05-20 0:17 Sam James
2022-05-16 20:00 Arthur Zamarin
2022-05-16 19:38 Arthur Zamarin
2022-05-15 11:14 Jakov Smolić
2022-05-15 8:38 Jakov Smolić
2022-05-15 8:38 Jakov Smolić
2022-05-15 8:21 Jakov Smolić
2022-05-15 8:19 Jakov Smolić
2022-05-11 20:11 Michał Górny
2022-05-11 17:15 Arthur Zamarin
2022-05-11 17:15 Arthur Zamarin
2022-05-11 12:56 Jakov Smolić
2022-05-01 21:51 Jakov Smolić
2022-04-10 12:35 James Le Cuirot
2022-04-09 19:47 Arthur Zamarin
2022-04-09 19:23 Arthur Zamarin
2022-04-08 14:25 Arthur Zamarin
2022-04-08 14:25 Arthur Zamarin
2022-04-08 14:23 Arthur Zamarin
2022-04-07 15:31 Jakov Smolić
2022-04-07 9:49 Michał Górny
2021-12-12 21:32 Michał Górny
2021-12-12 19:56 Jakov Smolić
2021-12-09 22:39 Michał Górny
2021-12-09 21:24 Sam James
2021-11-12 9:40 Michał Górny
2021-11-03 20:53 Michał Górny
2021-09-27 8:40 James Le Cuirot
2021-07-28 23:38 Marek Szuba
2021-05-29 21:34 Michał Górny
2021-05-29 21:34 Michał Górny
2021-04-21 19:25 Michał Górny
2021-04-21 18:55 Sam James
2021-03-19 7:36 Michał Górny
2021-03-14 22:39 Michał Górny
2021-03-14 22:33 Sam James
2021-02-10 8:06 Michał Górny
2021-01-13 20:16 Michał Górny
2021-01-13 19:06 Sam James
2020-12-11 7:33 Michał Górny
2020-11-28 15:36 Sam James
2020-08-23 17:06 Sam James
2020-08-14 23:22 Andreas Sturmlechner
2020-07-25 10:22 Michał Górny
2020-07-12 2:41 Sam James
2020-07-11 8:57 Michał Górny
2020-05-26 16:57 Michał Górny
2020-05-26 16:57 Michał Górny
2020-05-26 16:57 Michał Górny
2020-05-26 16:23 Michał Górny
2020-03-03 7:22 Matt Turner
2020-01-26 21:46 Matthew Thode
2019-12-08 23:31 Sergei Trofimovich
2019-12-07 23:07 Matt Turner
2019-12-03 16:24 Jeroen Roovers
2019-12-01 13:59 Sergei Trofimovich
2019-12-01 13:52 Sergei Trofimovich
2019-11-30 4:30 Aaron Bauman
2019-11-29 23:03 Sergei Trofimovich
2019-11-27 13:05 Mikle Kolyada
2019-11-27 2:18 Patrick McLean
2019-11-27 1:51 Patrick McLean
2019-11-27 1:13 Patrick McLean
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=1594457851.e22e72d3e8f910320b723eacca99616e0f5e85d1.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