From: "Ronny Gutbrod" <gentoo@tastytea.de> To: gentoo-commits@lists.gentoo.org Subject: [gentoo-commits] repo/proj/guru:dev commit in: dev-python/microversion-parse/ Date: Fri, 25 Mar 2022 11:23:48 +0000 (UTC) [thread overview] Message-ID: <1648203186.e3c59188b6d71e8d0f1e3776f61f324694d84adc.tastytea@gentoo> (raw) commit: e3c59188b6d71e8d0f1e3776f61f324694d84adc Author: Ronny (tastytea) Gutbrod <gentoo <AT> tastytea <DOT> de> AuthorDate: Fri Mar 25 10:13:06 2022 +0000 Commit: Ronny Gutbrod <gentoo <AT> tastytea <DOT> de> CommitDate: Fri Mar 25 10:13:06 2022 +0000 URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=e3c59188 dev-python/microversion-parse: update upstream metadata Old URL is a permanent redirect to new URL. Signed-off-by: Ronny (tastytea) Gutbrod <gentoo <AT> tastytea.de> dev-python/microversion-parse/metadata.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dev-python/microversion-parse/metadata.xml b/dev-python/microversion-parse/metadata.xml index 27b58d66a..7f1166125 100644 --- a/dev-python/microversion-parse/metadata.xml +++ b/dev-python/microversion-parse/metadata.xml @@ -4,7 +4,7 @@ <!-- maintainer-needed --> <stabilize-allarches/> <upstream> - <remote-id type="pypi">microversion_parse</remote-id> + <remote-id type="pypi">microversion-parse</remote-id> <remote-id type="github">openstack/microversion-parse</remote-id> </upstream> </pkgmetadata>
WARNING: multiple messages have this Message-ID (diff)
From: "Ronny Gutbrod" <gentoo@tastytea.de> To: gentoo-commits@lists.gentoo.org Subject: [gentoo-commits] repo/proj/guru:master commit in: dev-python/microversion-parse/ Date: Fri, 25 Mar 2022 15:17:03 +0000 (UTC) [thread overview] Message-ID: <1648203186.e3c59188b6d71e8d0f1e3776f61f324694d84adc.tastytea@gentoo> (raw) Message-ID: <20220325151703.0yRb6WUFSjrAy1Ek07_tVhgGMLE972AFy5Aocgf_pT4@z> (raw) commit: e3c59188b6d71e8d0f1e3776f61f324694d84adc Author: Ronny (tastytea) Gutbrod <gentoo <AT> tastytea <DOT> de> AuthorDate: Fri Mar 25 10:13:06 2022 +0000 Commit: Ronny Gutbrod <gentoo <AT> tastytea <DOT> de> CommitDate: Fri Mar 25 10:13:06 2022 +0000 URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=e3c59188 dev-python/microversion-parse: update upstream metadata Old URL is a permanent redirect to new URL. Signed-off-by: Ronny (tastytea) Gutbrod <gentoo <AT> tastytea.de> dev-python/microversion-parse/metadata.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dev-python/microversion-parse/metadata.xml b/dev-python/microversion-parse/metadata.xml index 27b58d66a..7f1166125 100644 --- a/dev-python/microversion-parse/metadata.xml +++ b/dev-python/microversion-parse/metadata.xml @@ -4,7 +4,7 @@ <!-- maintainer-needed --> <stabilize-allarches/> <upstream> - <remote-id type="pypi">microversion_parse</remote-id> + <remote-id type="pypi">microversion-parse</remote-id> <remote-id type="github">openstack/microversion-parse</remote-id> </upstream> </pkgmetadata>
next reply other threads:[~2022-03-25 11:23 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-25 11:23 Ronny Gutbrod [this message] 2022-03-25 15:17 ` [gentoo-commits] repo/proj/guru:master commit in: dev-python/microversion-parse/ Ronny Gutbrod -- strict thread matches above, loose matches on Subject: below -- 2022-03-20 16:46 [gentoo-commits] repo/proj/guru:dev " Alessandro Barbieri
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=1648203186.e3c59188b6d71e8d0f1e3776f61f324694d84adc.tastytea@gentoo \ --to=gentoo@tastytea.de \ --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: linkBe 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