From: "David Seifert" <soap@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-text/xmldiff/
Date: Sat, 25 Nov 2017 19:55:35 +0000 (UTC) [thread overview]
Message-ID: <1511639715.b9099b22d774d781c0ab02e85db7742f4bbedd1b.soap@gentoo> (raw)
commit: b9099b22d774d781c0ab02e85db7742f4bbedd1b
Author: David Seifert <soap <AT> gentoo <DOT> org>
AuthorDate: Sat Nov 25 18:09:57 2017 +0000
Commit: David Seifert <soap <AT> gentoo <DOT> org>
CommitDate: Sat Nov 25 19:55:15 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b9099b22
app-text/xmldiff: [QA] Consistent whitespace in metadata.xml
app-text/xmldiff/metadata.xml | 21 +++++++++++----------
1 file changed, 11 insertions(+), 10 deletions(-)
diff --git a/app-text/xmldiff/metadata.xml b/app-text/xmldiff/metadata.xml
index 5ad26e1522f..e7734cc5fb8 100644
--- a/app-text/xmldiff/metadata.xml
+++ b/app-text/xmldiff/metadata.xml
@@ -1,14 +1,15 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
- <maintainer type="person">
- <email>xmw@gentoo.org</email>
- <name>Michael Weber</name>
- </maintainer>
- <longdescription>A python tool that figures out the differences between two
- similar XML files, in the same way the diff utility does.
- Xmldiff was initially developed for the Narval project and could also be
- used as a library or as a command line tool. It can work either with XML
- files or DOM trees.
- </longdescription>
+ <maintainer type="person">
+ <email>xmw@gentoo.org</email>
+ <name>Michael Weber</name>
+ </maintainer>
+ <longdescription>
+ A python tool that figures out the differences between two
+ similar XML files, in the same way the diff utility does.
+ Xmldiff was initially developed for the Narval project and could also be
+ used as a library or as a command line tool. It can work either with XML
+ files or DOM trees.
+ </longdescription>
</pkgmetadata>
next reply other threads:[~2017-11-25 19:55 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-25 19:55 David Seifert [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-29 19:03 [gentoo-commits] repo/gentoo:master commit in: app-text/xmldiff/ Andreas Sturmlechner
2023-12-30 6:38 Arthur Zamarin
2023-12-30 6:38 Arthur Zamarin
2023-12-29 21:41 Sam James
2023-12-29 19:20 Arthur Zamarin
2023-11-22 12:02 Sam James
2023-11-22 12:02 Sam James
2022-11-20 4:52 Sam James
2021-08-17 22:52 Louis Sautier
2021-04-19 19:41 Sam James
2021-01-05 20:51 Sam James
2021-01-03 11:51 Sergei Trofimovich
2021-01-01 11:21 Sergei Trofimovich
2020-12-29 9:52 Sam James
2020-10-10 7:22 Joonas Niilola
2020-08-01 22:57 Andreas Sturmlechner
2020-08-01 9:14 Sergei Trofimovich
2020-07-29 23:41 Sam James
2020-07-28 14:11 Sam James
2020-07-27 2:14 Sam James
2020-04-17 0:04 Andreas Sturmlechner
2020-04-05 7:18 Joonas Niilola
2020-04-05 7:18 Joonas Niilola
2020-02-11 11:38 Michał Górny
2019-06-05 7:46 Agostino Sarubbo
2019-05-02 21:05 Mikle Kolyada
2019-03-17 23:02 Sergei Trofimovich
2019-03-16 18:40 Sergei Trofimovich
2019-03-15 8:12 Mikle Kolyada
2019-02-02 20:44 Sergei Trofimovich
2018-08-19 21:13 Michael Weber
2018-04-21 7:53 Michał Górny
2017-02-10 18:55 Pacho Ramos
2016-10-18 19:26 Pacho Ramos
2016-10-16 17:45 Tobias Klausmann
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=1511639715.b9099b22d774d781c0ab02e85db7742f4bbedd1b.soap@gentoo \
--to=soap@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