public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Joonas Niilola" <juippis@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/dqlite/
Date: Tue, 13 Dec 2022 14:25:14 +0000 (UTC)	[thread overview]
Message-ID: <1670941512.02b41bb36fd29d4f1a847c9f81425943ffeca31c.juippis@gentoo> (raw)

commit:     02b41bb36fd29d4f1a847c9f81425943ffeca31c
Author:     Joonas Niilola <juippis <AT> gentoo <DOT> org>
AuthorDate: Tue Dec 13 14:24:56 2022 +0000
Commit:     Joonas Niilola <juippis <AT> gentoo <DOT> org>
CommitDate: Tue Dec 13 14:25:12 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=02b41bb3

dev-libs/dqlite: add github upstream metadata

Signed-off-by: Joonas Niilola <juippis <AT> gentoo.org>

 dev-libs/dqlite/metadata.xml | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/dev-libs/dqlite/metadata.xml b/dev-libs/dqlite/metadata.xml
index 2a8b8beafdf7..93aa9821db98 100644
--- a/dev-libs/dqlite/metadata.xml
+++ b/dev-libs/dqlite/metadata.xml
@@ -18,4 +18,7 @@
     instances of your application and have them act as a highly-available 
     cluster, with no dependency on external databases.
   </longdescription>
+  <upstream>
+    <remote-id type="github">canonical/dqlite</remote-id>
+  </upstream>
 </pkgmetadata>


             reply	other threads:[~2022-12-13 14:25 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13 14:25 Joonas Niilola [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-31 12:58 [gentoo-commits] repo/gentoo:master commit in: dev-libs/dqlite/ Joonas Niilola
2025-03-31 12:58 Joonas Niilola
2024-08-20  5:20 Joonas Niilola
2024-08-20  5:20 Joonas Niilola
2024-07-30  5:26 Joonas Niilola
2024-03-17  7:45 Joonas Niilola
2024-02-28  4:30 Joonas Niilola
2024-02-25  9:36 Joonas Niilola
2024-02-25  9:36 Joonas Niilola
2024-02-23  7:19 Joonas Niilola
2024-02-20  9:08 Joonas Niilola
2024-02-19  9:16 Joonas Niilola
2023-11-01 13:17 Joonas Niilola
2023-10-23  5:55 Joonas Niilola
2023-09-22  6:09 Joonas Niilola
2023-07-18  5:22 Joonas Niilola
2023-07-16  6:56 Joonas Niilola
2023-06-29  6:41 Joonas Niilola
2023-06-15 12:14 Joonas Niilola
2023-06-13 12:48 Joonas Niilola
2023-02-22  7:14 Joonas Niilola
2023-02-20  8:06 Joonas Niilola
2023-01-22  7:24 Joonas Niilola
2023-01-19 15:10 Joonas Niilola
2023-01-15  7:11 Joonas Niilola
2023-01-09 12:51 Joonas Niilola
2023-01-04 13:51 Joonas Niilola
2022-12-13 14:25 Joonas Niilola
2022-11-19  7:37 Joonas Niilola
2022-08-24  7:02 Joonas Niilola
2022-08-16  7:55 Joonas Niilola
2022-07-14  5:30 Joonas Niilola
2022-06-04  7:07 Joonas Niilola
2022-05-16 14:26 Joonas Niilola
2022-04-14 11:51 Joonas Niilola
2022-04-14  8:54 Joonas Niilola
2022-03-20  6:22 Joonas Niilola
2022-02-14  9:07 Joonas Niilola
2021-10-04  5:40 Joonas Niilola
2021-09-10  5:42 Joonas Niilola
2021-09-09 11:30 Joonas Niilola
2021-09-09 11:30 Joonas Niilola
2021-08-09 14:26 Joonas Niilola
2021-07-19 11:15 Joonas Niilola
2021-07-10 14:45 Joonas Niilola
2021-06-10  6:31 Joonas Niilola
2021-06-01  8:43 Joonas Niilola
2021-06-01  8:43 Joonas Niilola
2021-04-30  7:01 Joonas Niilola
2020-12-09  8:04 Joonas Niilola
2020-11-15 14:59 Luca Barbato
2020-10-23  9:25 David Seifert
2020-10-23  8:06 Joonas Niilola
2020-10-23  7:37 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=1670941512.02b41bb36fd29d4f1a847c9f81425943ffeca31c.juippis@gentoo \
    --to=juippis@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