From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-devel/make/
Date: Wed, 21 Sep 2022 02:22:48 +0000 (UTC) [thread overview]
Message-ID: <1663726958.48d7190bec98c0a491159b68c80e31efbe62b496.sam@gentoo> (raw)
commit: 48d7190bec98c0a491159b68c80e31efbe62b496
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Sep 21 02:22:32 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Sep 21 02:22:38 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=48d7190b
sys-devel/make: fix metadata indentation
Signed-off-by: Sam James <sam <AT> gentoo.org>
sys-devel/make/metadata.xml | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/sys-devel/make/metadata.xml b/sys-devel/make/metadata.xml
index 1e62dd910293..fee78a624e6a 100644
--- a/sys-devel/make/metadata.xml
+++ b/sys-devel/make/metadata.xml
@@ -1,11 +1,11 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "https://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
-<maintainer type="project">
- <email>base-system@gentoo.org</email>
- <name>Gentoo Base System</name>
-</maintainer>
-<upstream>
- <remote-id type="cpe">cpe:/a:gnu:make</remote-id>
-</upstream>
+ <maintainer type="project">
+ <email>base-system@gentoo.org</email>
+ <name>Gentoo Base System</name>
+ </maintainer>
+ <upstream>
+ <remote-id type="cpe">cpe:/a:gnu:make</remote-id>
+ </upstream>
</pkgmetadata>
next reply other threads:[~2022-09-21 2:22 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 2:22 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-22 16:26 [gentoo-commits] repo/gentoo:master commit in: sys-devel/make/ David Seifert
2023-05-04 11:21 Sam James
2023-04-27 4:51 Sam James
2023-04-27 4:51 Sam James
2023-04-27 4:51 Sam James
2023-04-27 4:51 Sam James
2023-04-27 4:51 Sam James
2023-04-27 4:51 Sam James
2023-04-27 4:51 Sam James
2023-04-27 4:51 Sam James
2023-03-24 1:37 Sam James
2023-02-28 21:21 Sam James
2023-02-26 20:21 Sam James
2023-02-24 18:36 Sam James
2023-01-14 22:14 Sam James
2022-10-31 15:45 Sam James
2022-10-24 11:47 Sam James
2022-10-20 3:50 Sam James
2022-09-20 23:25 Sam James
2022-08-29 15:31 Sam James
2022-04-07 3:57 Sam James
2021-01-06 15:32 Fabian Groffen
2021-01-04 17:27 Sam James
2020-12-27 18:18 Fabian Groffen
2020-12-27 12:51 Sergei Trofimovich
2020-12-24 22:06 Sergei Trofimovich
2020-12-24 18:38 Sergei Trofimovich
2020-12-21 20:35 Sam James
2020-12-21 20:35 Sam James
2020-12-21 19:45 Sam James
2020-12-21 18:27 Sam James
2020-12-21 1:37 Thomas Deutschmann
2020-05-04 17:36 Thomas Deutschmann
2020-01-20 8:41 Lars Wendler
2020-01-17 16:59 Lars Wendler
2019-05-03 23:22 Mikle Kolyada
2018-08-31 3:26 Thomas Deutschmann
2018-08-04 13:51 Thomas Deutschmann
2018-05-30 12:03 Mart Raudsepp
2018-02-19 15:47 Lars Wendler
2018-02-10 23:41 Andreas Hüttel
2017-02-25 7:42 Markus Meier
2017-02-20 14:11 Michael Haubenwallner
2017-01-29 20:43 Jeroen Roovers
2017-01-29 20:14 Fabian Groffen
2017-01-26 11:00 Agostino Sarubbo
2017-01-25 13:52 Tobias Klausmann
2017-01-24 11:46 Agostino Sarubbo
2017-01-23 16:27 Agostino Sarubbo
2017-01-23 15:46 Agostino Sarubbo
2017-01-23 13:51 Agostino Sarubbo
2016-06-11 9:22 Lars Wendler
2016-05-22 15:32 Lars Wendler
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=1663726958.48d7190bec98c0a491159b68c80e31efbe62b496.sam@gentoo \
--to=sam@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