From: "Andrew Ammerlaan" <andrewammerlaan@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/backrefs/
Date: Sat, 22 May 2021 20:55:56 +0000 (UTC) [thread overview]
Message-ID: <1621716943.3f15e263c39ebf1ebb447d54cc7cbc65221fde8a.andrewammerlaan@gentoo> (raw)
commit: 3f15e263c39ebf1ebb447d54cc7cbc65221fde8a
Author: Andrew Ammerlaan <andrewammerlaan <AT> gentoo <DOT> org>
AuthorDate: Sat May 22 20:37:05 2021 +0000
Commit: Andrew Ammerlaan <andrewammerlaan <AT> gentoo <DOT> org>
CommitDate: Sat May 22 20:55:43 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3f15e263
dev-python/backrefs: add <stabilize-allarches/>
Package-Manager: Portage-3.0.18, Repoman-3.0.3
Signed-off-by: Andrew Ammerlaan <andrewammerlaan <AT> gentoo.org>
dev-python/backrefs/metadata.xml | 1 +
1 file changed, 1 insertion(+)
diff --git a/dev-python/backrefs/metadata.xml b/dev-python/backrefs/metadata.xml
index 0c26badc91b..8588059ebf5 100644
--- a/dev-python/backrefs/metadata.xml
+++ b/dev-python/backrefs/metadata.xml
@@ -20,4 +20,5 @@
<longdescription lang="en">
Backrefs is a wrapper around Python's built-in Re and the 3rd party Regex library. Backrefs adds various additional back references (and a couple other features) that are known to some regular expression engines, but not to Python's Re and/or Regex. The supported back references actually vary depending on the regular expression engine being used as the engine may already have support for some.
</longdescription>
+ <stabilize-allarches/>
</pkgmetadata>
next reply other threads:[~2021-05-22 20:56 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 20:55 Andrew Ammerlaan [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-06 6:36 [gentoo-commits] repo/gentoo:master commit in: dev-python/backrefs/ Michał Górny
2024-07-06 6:29 Sam James
2024-06-16 18:44 Michał Górny
2023-11-24 14:43 Michał Górny
2023-11-23 19:00 Michał Górny
2023-10-06 15:08 Michał Górny
2023-10-06 14:31 Sam James
2023-09-03 4:12 Michał Górny
2023-08-31 13:22 Michał Górny
2023-07-21 12:52 Arthur Zamarin
2023-07-21 12:35 Arthur Zamarin
2023-06-16 4:05 Michał Górny
2023-06-16 4:05 Michał Górny
2023-04-09 20:40 Andrew Ammerlaan
2022-11-30 2:55 Michał Górny
2022-11-29 22:22 Jakov Smolić
2022-10-28 7:09 Michał Górny
2022-10-28 7:09 Michał Górny
2022-06-22 5:33 Joonas Niilola
2022-05-22 16:36 Michał Górny
2022-05-22 16:15 Michał Górny
2022-05-22 16:15 Michał Górny
2022-05-22 5:53 Michał Górny
2021-11-21 20:14 Michał Górny
2021-11-21 19:36 Jakov Smolić
2021-11-03 6:43 Michał Górny
2021-10-20 9:40 Michał Górny
2021-09-23 15:35 Marek Szuba
2021-07-15 7:38 Agostino Sarubbo
2021-05-22 7:58 Michał Górny
2021-01-23 23:30 Michał Górny
2021-01-23 0:11 Michał Górny
2021-01-10 9:38 Michał Górny
2020-12-08 5:53 Joonas Niilola
2020-12-08 5:53 Joonas Niilola
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=1621716943.3f15e263c39ebf1ebb447d54cc7cbc65221fde8a.andrewammerlaan@gentoo \
--to=andrewammerlaan@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