From: "Alex Brandt" <alunduil@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/nose2/
Date: Sun, 27 Mar 2016 17:21:43 +0000 (UTC) [thread overview]
Message-ID: <1459099275.ad6cb0e7390aebdbb51e40c48d7f4ce84cd76437.alunduil@gentoo> (raw)
commit: ad6cb0e7390aebdbb51e40c48d7f4ce84cd76437
Author: Alex Brandt <alunduil <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 27 17:20:15 2016 +0000
Commit: Alex Brandt <alunduil <AT> gentoo <DOT> org>
CommitDate: Sun Mar 27 17:21:15 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ad6cb0e7
dev-python/nose2: add type to maintainer tag in metadata
I still wonder why the vim template doesn't include this in its
generation of metadata.xml but it can continue to wait. Also, why does
repoman commit break the automatic linebreaking done by vim in commit
messages?
Looks like ft=conf instead of the normal commit type?
Package-Manager: portage-2.2.28
dev-python/nose2/metadata.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-python/nose2/metadata.xml b/dev-python/nose2/metadata.xml
index 02be8c5..9b3c6f8 100644
--- a/dev-python/nose2/metadata.xml
+++ b/dev-python/nose2/metadata.xml
@@ -1,7 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
- <maintainer>
+ <maintainer type="person">
<email>alunduil@gentoo.org</email>
<name>Alex Brandt</name>
</maintainer>
next reply other threads:[~2016-03-27 17:21 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-27 17:21 Alex Brandt [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-10 13:20 [gentoo-commits] repo/gentoo:master commit in: dev-python/nose2/ Michał Górny
2024-06-18 18:45 Michał Górny
2024-06-02 2:35 Michał Górny
2024-05-31 4:22 Michał Górny
2024-05-22 9:10 Michał Górny
2024-05-07 17:45 Michał Górny
2024-02-14 12:36 Michał Górny
2024-02-14 12:26 Michał Górny
2024-01-29 9:21 Michał Górny
2024-01-29 5:58 Michał Górny
2023-11-05 20:58 Michał Górny
2023-11-05 19:10 Arthur Zamarin
2023-10-05 2:58 Michał Górny
2023-06-01 17:19 Arthur Zamarin
2023-04-30 3:55 Michał Górny
2023-03-16 18:13 Michał Górny
2022-07-29 8:01 Agostino Sarubbo
2022-07-28 14:14 Sam James
2022-07-28 9:57 Sam James
2022-07-28 7:06 Agostino Sarubbo
2022-07-27 20:09 Sam James
2022-07-27 20:09 Sam James
2022-07-17 7:22 Michał Górny
2022-03-19 9:36 Michał Górny
2022-02-15 18:31 Matt Turner
2022-02-13 9:29 Michał Górny
2021-11-19 17:36 Arthur Zamarin
2021-11-19 7:24 Arthur Zamarin
2021-11-17 8:30 Sam James
2021-11-16 19:10 Arthur Zamarin
2021-09-27 9:29 Arthur Zamarin
2021-04-07 8:06 Michał Górny
2021-04-07 6:22 Sam James
2021-03-04 4:19 Sam James
2021-01-04 3:36 Sam James
2021-01-04 3:31 Sam James
2021-01-04 1:25 Sam James
2020-12-02 23:32 Sam James
2019-12-08 12:04 Andreas Sturmlechner
2019-12-06 20:21 Andreas Sturmlechner
2019-11-23 12:43 Agostino Sarubbo
2019-11-22 10:24 Agostino Sarubbo
2019-10-26 14:33 Andreas Sturmlechner
2019-10-20 14:21 Andreas Sturmlechner
2019-04-14 11:12 Agostino Sarubbo
2017-11-30 20:40 Thomas Deutschmann
2016-07-16 14:28 Alex Brandt
2016-03-27 14:28 Alex Brandt
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=1459099275.ad6cb0e7390aebdbb51e40c48d7f4ce84cd76437.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