From: "Manuel Rüger" <mrueg@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-fs/minio/
Date: Tue, 28 Nov 2017 16:02:46 +0000 (UTC) [thread overview]
Message-ID: <1511884945.60c76b43e13786091a155f3dac6b645ca1a13f34.mrueg@gentoo> (raw)
commit: 60c76b43e13786091a155f3dac6b645ca1a13f34
Author: Manuel Rüger <mrueg <AT> gentoo <DOT> org>
AuthorDate: Tue Nov 28 16:02:25 2017 +0000
Commit: Manuel Rüger <mrueg <AT> gentoo <DOT> org>
CommitDate: Tue Nov 28 16:02:25 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=60c76b43
net-fs/minio: Add github upstream
Package-Manager: Portage-2.3.16, Repoman-2.3.6
net-fs/minio/metadata.xml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/net-fs/minio/metadata.xml b/net-fs/minio/metadata.xml
index 97df2a00971..1ec71a5fdd1 100644
--- a/net-fs/minio/metadata.xml
+++ b/net-fs/minio/metadata.xml
@@ -5,4 +5,7 @@
<email>mrueg@gentoo.org</email>
<name>Manuel Rüger</name>
</maintainer>
+ <upstream>
+ <remote-id type="github">minio/minio</remote-id>
+ </upstream>
</pkgmetadata>
next reply other threads:[~2017-11-28 16:02 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 16:02 Manuel Rüger [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-09-29 7:34 [gentoo-commits] repo/gentoo:master commit in: net-fs/minio/ Jakov Smolić
2022-09-10 21:11 William Hubbs
2021-04-19 18:37 Mike Gilbert
2021-04-19 14:00 Mikle Kolyada
2021-04-19 14:00 Mikle Kolyada
2021-04-19 13:24 Mikle Kolyada
2021-04-19 13:14 Mikle Kolyada
2021-04-19 13:05 Mikle Kolyada
2021-04-09 17:18 Mikle Kolyada
2021-04-06 21:48 John Helmert III
2021-03-27 14:16 Mikle Kolyada
2021-03-21 17:56 Mikle Kolyada
2021-03-12 14:02 Mikle Kolyada
2021-03-09 15:39 Mikle Kolyada
2021-03-09 15:39 Mikle Kolyada
2021-02-07 18:40 Mikle Kolyada
2021-01-26 14:37 Mikle Kolyada
2021-01-26 14:37 Mikle Kolyada
2021-01-26 13:22 Mikle Kolyada
2020-06-22 22:24 William Hubbs
2019-09-21 17:12 Mikle Kolyada
2019-09-13 16:57 Mikle Kolyada
2019-08-31 14:16 Mikle Kolyada
2019-08-22 11:26 Mikle Kolyada
2019-08-16 19:36 Mikle Kolyada
2019-08-16 19:31 Mikle Kolyada
2019-08-02 18:37 Mikle Kolyada
2019-08-01 8:48 Mikle Kolyada
2019-07-25 20:55 Mikle Kolyada
2019-07-25 12:47 Mikle Kolyada
2019-06-23 11:01 Mikle Kolyada
2019-04-28 12:38 Mikle Kolyada
2019-04-09 12:26 Mikle Kolyada
2019-04-05 12:46 Mikle Kolyada
2019-03-28 7:39 Mikle Kolyada
2019-03-21 22:10 Mikle Kolyada
2019-03-14 18:10 Mikle Kolyada
2019-03-12 16:04 Mikle Kolyada
2019-03-12 16:04 Mikle Kolyada
2019-03-07 17:05 Mikle Kolyada
2019-02-28 10:45 Mikle Kolyada
2019-02-21 17:50 Mikle Kolyada
2019-02-15 6:17 Mikle Kolyada
2019-02-13 10:01 Mikle Kolyada
2019-02-07 10:06 Mikle Kolyada
2019-01-31 14:19 Mikle Kolyada
2019-01-30 9:16 Mikle Kolyada
2019-01-25 8:25 Mikle Kolyada
2019-01-17 17:11 Mikle Kolyada
2019-01-10 9:07 Mikle Kolyada
2019-01-09 8:03 Fabian Groffen
2018-12-28 6:27 Mikle Kolyada
2018-12-20 17:55 Mikle Kolyada
2018-12-13 20:33 Mikle Kolyada
2018-12-06 18:12 Mikle Kolyada
2018-11-30 20:46 Mikle Kolyada
2018-11-30 11:13 Mikle Kolyada
2018-11-22 15:18 Mikle Kolyada
2018-11-17 7:15 Mikle Kolyada
2018-11-15 14:10 Mikle Kolyada
2018-11-10 12:40 Mikle Kolyada
2018-10-25 19:49 Mikle Kolyada
2018-10-25 17:42 Mikle Kolyada
2018-10-19 20:17 Mikle Kolyada
2018-10-12 13:11 Mikle Kolyada
2018-09-28 8:25 Mikle Kolyada
2018-09-13 12:12 Mikle Kolyada
2018-09-09 10:43 Mikle Kolyada
2018-08-13 2:36 Mikle Kolyada
2018-08-05 13:08 Manuel Rüger
2018-07-24 15:23 Manuel Rüger
2018-06-06 12:31 Manuel Rüger
2018-05-17 15:21 Manuel Rüger
2018-04-26 1:47 Manuel Rüger
2018-04-13 14:10 Manuel Rüger
2018-03-30 14:19 Manuel Rüger
2018-03-30 14:19 Manuel Rüger
2018-02-27 12:50 Manuel Rüger
2017-11-27 19:31 Manuel Rüger
2017-11-20 18:11 Manuel Rüger
2017-11-20 18:11 Manuel Rüger
2017-10-20 12:13 Manuel Rüger
2017-09-10 12:18 Manuel Rüger
2017-06-23 17:58 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=1511884945.60c76b43e13786091a155f3dac6b645ca1a13f34.mrueg@gentoo \
--to=mrueg@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