public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/XML-LibXSLT/
Date: Wed, 10 May 2023 22:07:17 +0000 (UTC)	[thread overview]
Message-ID: <1683756408.0ed93d2820c324d4c97fe691b870cd251f5c132a.sam@gentoo> (raw)

commit:     0ed93d2820c324d4c97fe691b870cd251f5c132a
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed May 10 22:06:48 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed May 10 22:06:48 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0ed93d28

dev-perl/XML-LibXSLT: add github upstream metadata

Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-perl/XML-LibXSLT/metadata.xml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/dev-perl/XML-LibXSLT/metadata.xml b/dev-perl/XML-LibXSLT/metadata.xml
index 7a635fb28c29..f3584055090c 100644
--- a/dev-perl/XML-LibXSLT/metadata.xml
+++ b/dev-perl/XML-LibXSLT/metadata.xml
@@ -14,5 +14,6 @@
     <remote-id type="cpan-module">XML::LibXSLT</remote-id>
     <remote-id type="cpan-module">XML::LibXSLT::Security</remote-id>
     <remote-id type="cpan-module">XML::LibXSLT::StylesheetWrapper</remote-id>
+    <remote-id type="github">shlomif/perl-XML-LibXSLT</remote-id>
   </upstream>
 </pkgmetadata>


             reply	other threads:[~2023-05-10 22:07 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-10 22:07 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-16 21:14 [gentoo-commits] repo/gentoo:master commit in: dev-perl/XML-LibXSLT/ Sam James
2024-09-24 16:15 Arthur Zamarin
2024-09-23 17:30 Arthur Zamarin
2024-09-23 17:30 Arthur Zamarin
2024-09-23 17:30 Arthur Zamarin
2024-09-23 13:53 Sam James
2024-09-23 12:38 Sam James
2024-07-11  2:40 Ionen Wolkens
2024-07-07 11:02 Sam James
2024-06-23 17:47 Arthur Zamarin
2024-06-20 15:07 Ionen Wolkens
2024-05-28 18:23 Arthur Zamarin
2024-05-26  6:06 Arthur Zamarin
2023-03-24 13:20 Arthur Zamarin
2023-03-24 13:13 Arthur Zamarin
2023-03-22  6:04 Sam James
2023-03-22  5:27 Sam James
2023-03-22  5:27 Sam James
2023-03-22  5:27 Sam James
2023-03-04  7:12 Arthur Zamarin
2023-03-04  7:04 Arthur Zamarin
2023-03-04  7:04 Arthur Zamarin
2023-03-04  6:05 Arthur Zamarin
2023-03-04  5:56 Arthur Zamarin
2023-03-04  5:47 Arthur Zamarin
2023-02-12  6:41 Sam James
2022-12-06  7:32 Sam James
2022-11-18  5:00 Sam James
2021-12-11 15:52 Andreas K. Hüttel
2021-12-06  0:13 Sam James
2021-12-05  5:09 Sam James
2021-12-05  4:50 Sam James
2021-12-05  4:46 Sam James
2021-12-05  4:43 Sam James
2021-12-05  3:31 Sam James
2021-10-26  1:21 Yixun Lan
2021-10-16  0:48 Sam James
2021-10-06 12:07 Andreas K. Hüttel
2021-08-02  2:24 Sam James
2020-07-21 19:54 Kent Fredric
2019-10-11 19:38 Andreas K. Hüttel
2018-07-13 12:25 Mikle Kolyada
2018-06-06 23:23 Thomas Deutschmann
2018-06-06  5:24 Robin H. Johnson
2017-08-15 12:41 Andreas Hüttel
2017-06-15 16:27 Markus Meier
2017-01-03 11:29 Andreas Hüttel
2016-12-20 20:09 Thomas Deutschmann
2016-12-20 18:08 Tobias Klausmann
2016-09-24 18:58 Andreas Hüttel
2016-09-24 18:58 Andreas Hüttel

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=1683756408.0ed93d2820c324d4c97fe691b870cd251f5c132a.sam@gentoo \
    --to=sam@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