public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Marek Szuba" <marecki@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-crypt/yubikey-manager-qt/
Date: Mon, 13 Feb 2023 09:26:02 +0000 (UTC)	[thread overview]
Message-ID: <1676280348.e74163b94cb23e4c8e197a5b1aaeb4078a45ca06.marecki@gentoo> (raw)

commit:     e74163b94cb23e4c8e197a5b1aaeb4078a45ca06
Author:     Marek Szuba <marecki <AT> gentoo <DOT> org>
AuthorDate: Mon Feb 13 09:25:12 2023 +0000
Commit:     Marek Szuba <marecki <AT> gentoo <DOT> org>
CommitDate: Mon Feb 13 09:25:48 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e74163b9

app-crypt/yubikey-manager-qt: add github upstream metadata

Signed-off-by: Marek Szuba <marecki <AT> gentoo.org>

 app-crypt/yubikey-manager-qt/metadata.xml | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/app-crypt/yubikey-manager-qt/metadata.xml b/app-crypt/yubikey-manager-qt/metadata.xml
index ea19cfc370a2..1f472919c5a5 100644
--- a/app-crypt/yubikey-manager-qt/metadata.xml
+++ b/app-crypt/yubikey-manager-qt/metadata.xml
@@ -5,4 +5,7 @@
     <email>zerochaos@gentoo.org</email>
     <name>Rick Farina</name>
   </maintainer>
+  <upstream>
+    <remote-id type="github">Yubico/yubikey-manager-qt</remote-id>
+  </upstream>
 </pkgmetadata>


             reply	other threads:[~2023-02-13  9:26 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13  9:26 Marek Szuba [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-05-02  8:23 [gentoo-commits] repo/gentoo:master commit in: app-crypt/yubikey-manager-qt/ David Seifert
2024-03-05 15:00 Marek Szuba
2024-03-05 14:03 Marek Szuba
2023-06-04 15:49 Arthur Zamarin
2023-03-12 16:19 David Seifert
2023-03-12 16:14 David Seifert
2023-02-21 17:27 Michał Górny
2023-02-13  9:26 Marek Szuba
2023-02-13  9:26 Marek Szuba
2023-02-13  9:26 Marek Szuba
2022-08-07 15:39 David Seifert
2021-12-31  1:15 Georgy Yakovlev
2021-12-31  1:15 Georgy Yakovlev
2021-11-17 13:03 Marek Szuba
2021-08-10  0:22 Göktürk Yüksek
2021-05-14 14:25 Rick Farina
2021-04-03 21:58 Sam James
2021-02-17 15:34 Rick Farina
2021-02-15  2:19 Rick Farina
2020-10-06  1:36 Göktürk Yüksek
2020-06-04 20:59 Andreas Sturmlechner
2020-03-19  2:22 Rick Farina
2020-03-19  2:11 Rick Farina
2020-02-10 20:22 Göktürk Yüksek
2019-11-29  4:32 Göktürk Yüksek
2019-10-11 20:50 Göktürk Yüksek
2019-08-05  4:43 Göktürk Yüksek
2019-08-05  4:43 Göktürk Yüksek
2019-07-21 17:43 Michał Górny
2019-03-13  2:20 Göktürk Yüksek
2019-02-01  2:19 Göktürk Yüksek
2019-02-01  2:19 Göktürk Yüksek
2019-02-01  2:19 Göktürk Yüksek
2018-12-19 20:41 Rick Farina
2018-12-19 17:42 Rick Farina
2018-10-02 19:19 Richard Farina
2018-10-02 19:19 Richard Farina
2018-07-17 22:35 Göktürk Yüksek
2018-05-22 19:22 Göktürk Yüksek
2018-04-26  3:32 Andreas Sturmlechner
2018-02-22 10:51 Andreas Sturmlechner
2017-12-28 22:09 Göktürk Yüksek
2017-12-21  0:50 Göktürk Yüksek
2017-12-21  0:50 Göktürk Yüksek
2017-11-24 23:09 Michael Palimaka
2017-11-21 18:00 Manuel Rüger
2017-10-27 11:14 Manuel Rüger
2017-09-20 13:57 Manuel Rüger
2017-09-08 21:48 Manuel Rüger
2017-08-01 12:03 Manuel Rüger

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=1676280348.e74163b94cb23e4c8e197a5b1aaeb4078a45ca06.marecki@gentoo \
    --to=marecki@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