From: "Alex Brandt" <alunduil@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/s3transfer/
Date: Sat, 3 Sep 2016 14:30:27 +0000 (UTC) [thread overview]
Message-ID: <1472913005.1b6547d96661dd174db60eaecc6e631b147bdfe5.alunduil@gentoo> (raw)
commit: 1b6547d96661dd174db60eaecc6e631b147bdfe5
Author: Alex Brandt <alunduil <AT> gentoo <DOT> org>
AuthorDate: Sat Sep 3 14:30:05 2016 +0000
Commit: Alex Brandt <alunduil <AT> gentoo <DOT> org>
CommitDate: Sat Sep 3 14:30:05 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1b6547d9
dev-python/s3transfer: rectify metadata overwrite
xiamao pointed out that I accidentally threw this work overtop of
existing work. He suggested I at least merge the metadata with that in
6d3d8a71c0e825a77ced7588ddd5133026e07992 and this commit does that.
If there are any other problems due to this error, I'm sorry and feel
free to perform any necessary cleanups.
Package-Manager: portage-2.3.0
dev-python/s3transfer/metadata.xml | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/dev-python/s3transfer/metadata.xml b/dev-python/s3transfer/metadata.xml
index 3e6df16..f8698a1 100644
--- a/dev-python/s3transfer/metadata.xml
+++ b/dev-python/s3transfer/metadata.xml
@@ -8,6 +8,10 @@
<email>alunduil@gentoo.org</email>
<name>Alex Brandt</name>
</maintainer>
+ <maintainer type="person">
+ <email>klausman@gentoo.org</email>
+ <name>Tobias Klausmann</name>
+ </maintainer>
<longdescription lang="en">
</longdescription>
</pkgmetadata>
next reply other threads:[~2016-09-03 14:30 UTC|newest]
Thread overview: 140+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-03 14:30 Alex Brandt [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-21 21:30 [gentoo-commits] repo/gentoo:master commit in: dev-python/s3transfer/ Sam James
2025-09-10 6:04 Michał Górny
2025-08-02 12:02 Arthur Zamarin
2025-07-19 5:41 Michał Górny
2025-06-07 9:28 Michał Górny
2025-06-07 9:18 Michał Górny
2025-05-23 3:29 Michał Górny
2025-05-10 11:59 Michał Górny
2025-05-10 11:04 Sam James
2025-05-03 12:21 Michał Górny
2025-05-03 12:08 Arthur Zamarin
2025-04-23 5:35 Michał Górny
2025-04-18 3:11 Michał Górny
2025-03-22 11:41 Michał Górny
2025-03-22 11:28 Arthur Zamarin
2025-03-15 12:26 Michał Górny
2025-03-15 12:16 Arthur Zamarin
2025-03-05 6:25 Michał Górny
2025-02-27 5:50 Michał Górny
2025-02-01 11:35 Arthur Zamarin
2025-02-01 10:05 Michał Górny
2025-01-24 7:21 Michał Górny
2025-01-16 5:11 Michał Górny
2025-01-14 6:05 WANG Xuerui
2024-12-07 11:52 Michał Górny
2024-12-07 11:06 Arthur Zamarin
2024-11-21 6:01 Michał Górny
2024-10-26 13:07 Michał Górny
2024-10-26 12:48 Arthur Zamarin
2024-10-09 6:31 Michał Górny
2024-07-27 9:44 Michał Górny
2024-07-27 6:40 Arthur Zamarin
2024-07-06 19:35 Michał Górny
2024-06-25 8:01 Michał Górny
2024-03-30 14:27 Michał Górny
2024-03-30 14:25 Michał Górny
2024-03-15 5:05 Michał Górny
2024-01-06 9:54 Michał Górny
2024-01-06 9:50 Michał Górny
2023-12-30 14:40 Michał Górny
2023-12-22 8:30 Michał Górny
2023-12-15 13:13 Michał Górny
2023-12-15 12:55 Arthur Zamarin
2023-12-14 8:28 Michał Górny
2023-11-30 5:48 Michał Górny
2023-11-29 7:44 Michał Górny
2023-11-28 5:26 Michał Górny
2023-10-20 20:13 Michał Górny
2023-10-20 11:48 Sam James
2023-09-27 5:56 Michał Górny
2023-09-17 4:44 Michał Górny
2023-09-16 22:58 Sam James
2023-08-16 4:19 Michał Górny
2023-08-16 4:19 Michał Górny
2023-06-06 5:57 Michał Górny
2023-06-05 19:56 Arthur Zamarin
2023-05-05 5:21 Michał Górny
2023-01-10 14:50 Michał Górny
2022-12-21 6:46 Michał Górny
2022-06-19 5:06 Michał Górny
2022-06-18 20:25 Sam James
2022-06-01 7:21 Michał Górny
2022-05-14 20:01 Michał Górny
2022-03-16 8:07 Michał Górny
2022-03-15 17:56 Jakov Smolić
2022-02-24 22:00 Michał Górny
2022-02-02 23:21 Michał Górny
2021-12-09 22:51 Michał Górny
2021-12-09 22:01 Arthur Zamarin
2021-11-09 10:23 Michał Górny
2021-08-16 6:13 Michał Górny
2021-08-16 5:13 Agostino Sarubbo
2021-07-16 6:54 Michał Górny
2021-06-15 7:06 Agostino Sarubbo
2021-06-04 16:13 Michał Górny
2021-05-19 6:02 Michał Górny
2021-05-18 23:20 Sam James
2021-05-18 17:28 Sam James
2021-05-15 19:28 Sam James
2021-04-23 7:25 Michał Górny
2021-04-22 12:08 Sam James
2021-04-22 7:36 Michał Górny
2021-04-19 21:22 Michał Górny
2021-04-14 7:19 Michał Górny
2021-03-19 7:36 Michał Górny
2021-03-18 23:11 Michał Górny
2021-03-02 9:06 Michał Górny
2021-03-02 7:39 Sam James
2021-01-11 21:22 Michał Górny
2020-08-05 15:18 Michał Górny
2020-07-29 10:20 Michał Górny
2020-06-22 6:57 Agostino Sarubbo
2020-06-10 14:02 Michał Górny
2020-06-10 14:02 Michał Górny
2020-06-06 17:38 Agostino Sarubbo
2020-05-28 18:20 Patrick McLean
2020-03-17 8:08 Michał Górny
2020-02-04 13:32 Michał Górny
2020-01-22 23:40 Thomas Deutschmann
2019-10-25 22:09 Andrey Utkin
2019-06-05 7:46 Agostino Sarubbo
2019-06-05 6:48 Agostino Sarubbo
2019-03-27 21:29 Andrey Utkin
2019-03-27 21:00 Andrey Utkin
2019-03-27 21:00 Andrey Utkin
2018-11-30 20:13 Mikle Kolyada
2018-11-27 21:55 Thomas Deutschmann
2018-09-19 0:04 Andrey Utkin
2018-05-13 22:45 Andrey Utkin
2018-05-13 22:45 Andrey Utkin
2018-05-13 22:45 Andrey Utkin
2018-05-13 22:45 Andrey Utkin
2018-03-10 14:56 Pacho Ramos
2018-02-13 20:21 Matt Thode
2018-01-06 0:21 Andrey Utkin
2018-01-06 0:21 Andrey Utkin
2018-01-05 18:06 Mike Gilbert
2017-12-28 7:25 Patrick Lauer
2017-10-04 8:57 Michał Górny
2017-09-30 0:38 Matt Thode
2017-09-16 6:46 Patrick Lauer
2017-07-31 18:12 Sebastien Fabbro
2017-05-22 7:23 Michał Górny
2017-05-02 13:11 Michał Górny
2017-03-10 17:24 Patrick Lauer
2016-10-28 20:56 Patrick Lauer
2016-10-20 17:30 Patrick Lauer
2016-10-16 1:43 Alex Brandt
2016-10-16 1:43 Alex Brandt
2016-10-16 1:43 Alex Brandt
2016-10-01 20:15 Patrick Lauer
2016-09-24 15:13 Alex Brandt
2016-09-24 15:13 Alex Brandt
2016-09-10 23:36 Alex Brandt
2016-09-10 23:36 Alex Brandt
2016-08-30 15:53 Alex Brandt
2016-08-13 15:35 Alex Brandt
2016-08-09 10:48 Patrick Lauer
2016-06-20 9:43 Patrick Lauer
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=1472913005.1b6547d96661dd174db60eaecc6e631b147bdfe5.alunduil@gentoo \
--to=alunduil@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