From: "NP Hardass" <np-hardass@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: x11-wm/marco/
Date: Wed, 27 Sep 2017 03:23:14 +0000 (UTC) [thread overview]
Message-ID: <1506482572.9a4e743d958e90f2fc67bbf5f019bd5a00893bd9.np-hardass@gentoo> (raw)
commit: 9a4e743d958e90f2fc67bbf5f019bd5a00893bd9
Author: NP-Hardass <NP-Hardass <AT> gentoo <DOT> org>
AuthorDate: Wed Sep 27 03:15:44 2017 +0000
Commit: NP Hardass <np-hardass <AT> gentoo <DOT> org>
CommitDate: Wed Sep 27 03:22:52 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9a4e743d
x11-wm/marco: Fix inconsistent metadata.xml spacing
Package-Manager: Portage-2.3.10, Repoman-2.3.3
x11-wm/marco/metadata.xml | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/x11-wm/marco/metadata.xml b/x11-wm/marco/metadata.xml
index 092aa1ba054..e5009557a91 100644
--- a/x11-wm/marco/metadata.xml
+++ b/x11-wm/marco/metadata.xml
@@ -1,14 +1,14 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
- <maintainer type="project">
- <email>mate@gentoo.org</email>
- <name>Gentoo MATE Desktop</name>
- </maintainer>
+ <maintainer type="project">
+ <email>mate@gentoo.org</email>
+ <name>Gentoo MATE Desktop</name>
+ </maintainer>
<use>
<flag name="gtk3">Build with GTK+3 instead of GTK+2</flag>
</use>
- <upstream>
- <remote-id type="github">mate-desktop/marco</remote-id>
- </upstream>
+ <upstream>
+ <remote-id type="github">mate-desktop/marco</remote-id>
+ </upstream>
</pkgmetadata>
next reply other threads:[~2017-09-27 3:23 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 3:23 NP Hardass [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-18 5:33 [gentoo-commits] repo/gentoo:master commit in: x11-wm/marco/ Michał Górny
2024-11-04 18:39 Andreas Sturmlechner
2024-10-06 7:17 Sam James
2024-09-17 20:00 Andreas Sturmlechner
2024-07-26 5:05 Eli Schwartz
2024-07-09 18:32 Pacho Ramos
2024-04-09 17:28 Arthur Zamarin
2024-04-09 17:28 Arthur Zamarin
2024-02-07 14:53 Joonas Niilola
2024-01-19 10:53 Sam James
2023-12-22 6:46 Sam James
2023-12-21 11:55 Sam James
2023-10-10 5:48 Joonas Niilola
2023-10-10 5:48 Joonas Niilola
2023-06-14 23:13 Sam James
2023-06-14 19:42 Sam James
2023-05-20 6:28 Sam James
2023-05-15 5:38 Sam James
2023-05-05 4:39 Sam James
2022-12-21 10:00 Andreas Sturmlechner
2022-12-16 20:39 Arthur Zamarin
2022-07-27 5:22 Sam James
2022-06-28 2:03 WANG Xuerui
2022-05-14 3:00 Sam James
2022-01-09 15:48 Andreas Sturmlechner
2021-12-10 20:10 Jakov Smolić
2021-12-10 11:35 Jakov Smolić
2021-06-30 22:43 Adam Feldman
2020-09-02 6:02 Adam Feldman
2020-08-07 3:18 Adam Feldman
2020-04-06 20:19 Adam Feldman
2019-08-17 4:23 Göktürk Yüksek
2019-07-07 18:48 Göktürk Yüksek
2019-07-07 18:48 Göktürk Yüksek
2019-06-22 4:06 Göktürk Yüksek
2019-05-12 21:04 Göktürk Yüksek
2019-04-14 21:25 Mikle Kolyada
2019-04-14 16:24 Mikle Kolyada
2019-04-14 15:27 Mikle Kolyada
2018-10-06 20:25 Mart Raudsepp
2018-09-09 23:53 Thomas Deutschmann
2018-02-11 15:03 Ettore Di Giacinto
2018-01-14 17:18 Ettore Di Giacinto
2017-03-14 10:03 Ettore Di Giacinto
2016-08-06 2:12 NP Hardass
2016-05-30 19:18 Mikle Kolyada
2016-03-26 2:37 NP Hardass
2016-03-15 17:53 Agostino Sarubbo
2016-03-06 8:09 Mikle Kolyada
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=1506482572.9a4e743d958e90f2fc67bbf5f019bd5a00893bd9.np-hardass@gentoo \
--to=np-hardass@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