From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/neovim-remote/
Date: Tue, 21 Feb 2023 17:06:05 +0000 (UTC) [thread overview]
Message-ID: <1676999150.f670ccafb4079c28ab58a06e257df5ec56340274.sam@gentoo> (raw)
commit: f670ccafb4079c28ab58a06e257df5ec56340274
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Feb 21 16:50:57 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Feb 21 17:05:50 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f670ccaf
dev-python/neovim-remote: add github upstream metadata
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-python/neovim-remote/metadata.xml | 1 +
1 file changed, 1 insertion(+)
diff --git a/dev-python/neovim-remote/metadata.xml b/dev-python/neovim-remote/metadata.xml
index bbf1e5633e11..4f5138e06ceb 100644
--- a/dev-python/neovim-remote/metadata.xml
+++ b/dev-python/neovim-remote/metadata.xml
@@ -14,6 +14,7 @@
<name>Python</name>
</maintainer>
<upstream>
+ <remote-id type="github">mhinz/neovim-remote</remote-id>
<remote-id type="pypi">neovim-remote</remote-id>
</upstream>
</pkgmetadata>
next reply other threads:[~2023-02-21 17:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 17:06 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-16 8:06 [gentoo-commits] repo/gentoo:master commit in: dev-python/neovim-remote/ Michał Górny
2022-06-04 19:57 Michał Górny
2022-05-20 8:29 Michał Górny
2022-05-16 13:20 Michał Górny
2022-05-07 9:35 Michał Górny
2022-05-05 8:16 Michał Górny
2021-06-01 0:28 Sam James
2021-06-01 0:28 Sam James
2021-06-01 0:28 Sam James
2020-09-29 10:26 Joonas Niilola
2020-09-29 10:26 Joonas Niilola
2020-04-24 5:52 Michał Górny
2020-03-28 9:20 Michał Górny
2019-10-09 5:22 Joonas Niilola
2019-05-19 0:04 Michael Palimaka
2019-04-20 19:01 Mikle Kolyada
2018-11-02 21:14 Michał Górny
2018-11-02 21:14 Michał Górny
2018-07-07 12:15 Jonas Stein
2018-01-05 17:43 Patrice Clement
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=1676999150.f670ccafb4079c28ab58a06e257df5ec56340274.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