From: "Mike Gilbert" <floppym@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-i18n/ibus-libpinyin/
Date: Thu, 31 Aug 2017 19:53:18 +0000 (UTC) [thread overview]
Message-ID: <1504209174.cf2ac6788ef7314f79afacaea083f94a603ea1cc.floppym@gentoo> (raw)
commit: cf2ac6788ef7314f79afacaea083f94a603ea1cc
Author: Arfrever Frehtes Taifersar Arahesis <Arfrever <AT> Apache <DOT> Org>
AuthorDate: Thu Aug 31 18:49:51 2017 +0000
Commit: Mike Gilbert <floppym <AT> gentoo <DOT> org>
CommitDate: Thu Aug 31 19:52:54 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cf2ac678
app-i18n/ibus-libpinyin: Use consistent indentation in metadata.xml.
app-i18n/ibus-libpinyin/metadata.xml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/app-i18n/ibus-libpinyin/metadata.xml b/app-i18n/ibus-libpinyin/metadata.xml
index fc22424da0d..83d60bcf58d 100644
--- a/app-i18n/ibus-libpinyin/metadata.xml
+++ b/app-i18n/ibus-libpinyin/metadata.xml
@@ -14,8 +14,8 @@
<name>Proxy Maintainers</name>
</maintainer>
<longdescription lang="en">
- PinYin engine for IBus platform. It provides a Chinese PinYin input method.
- </longdescription>
+ PinYin engine for IBus platform. It provides a Chinese PinYin input method.
+ </longdescription>
<use>
<flag name="boost">Compile against <pkg>dev-libs/boost</pkg> libraries</flag>
<flag name="opencc">Enable support for <pkg>app-i18n/opencc</pkg></flag>
next reply other threads:[~2017-08-31 19:53 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 19:53 Mike Gilbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-09 18:54 [gentoo-commits] repo/gentoo:master commit in: app-i18n/ibus-libpinyin/ Matt Turner
2024-05-19 12:14 Yixun Lan
2023-09-09 7:08 Joonas Niilola
2023-09-09 6:57 Joonas Niilola
2023-09-08 18:50 Arthur Zamarin
2023-09-08 7:18 Joonas Niilola
2023-05-15 5:42 Sam James
2023-05-15 5:42 Sam James
2023-05-08 12:35 Sam James
2023-05-08 12:35 Sam James
2023-03-05 15:19 Sam James
2023-03-05 15:19 Sam James
2023-02-28 19:10 Sam James
2023-02-28 18:34 Arthur Zamarin
2022-10-08 1:37 Yixun Lan
2022-09-05 12:42 Yixun Lan
2022-07-07 14:01 Yixun Lan
2022-07-04 7:10 Joonas Niilola
2022-07-04 7:10 Joonas Niilola
2022-06-23 23:13 Yixun Lan
2021-03-25 23:52 Conrad Kostecki
2020-12-07 18:14 Mike Gilbert
2020-09-04 15:11 Sam James
2020-08-30 17:14 Thomas Deutschmann
2020-08-30 8:57 Joonas Niilola
2020-08-26 3:23 Yixun Lan
2020-05-29 14:11 Yixun Lan
2020-05-29 14:11 Yixun Lan
2020-05-18 21:13 Agostino Sarubbo
2020-05-18 21:10 Agostino Sarubbo
2020-02-09 16:11 Michał Górny
2020-01-17 19:09 Mike Gilbert
2019-10-16 13:43 Yixun Lan
2019-10-14 11:50 Agostino Sarubbo
2019-10-14 11:16 Agostino Sarubbo
2019-10-09 7:37 Yixun Lan
2019-10-09 7:37 Yixun Lan
2019-10-09 7:37 Yixun Lan
2018-07-11 8:56 Tony Vroon
2018-07-11 8:56 Tony Vroon
2018-06-23 22:55 Jonas Stein
2018-02-21 20:34 Mike Gilbert
2018-02-21 20:34 Mike Gilbert
2017-11-28 18:36 Mike Gilbert
2017-11-01 20:54 Mike Gilbert
2017-09-11 18:39 Mike Gilbert
2017-08-31 19:53 Mike Gilbert
2017-08-22 14:21 Mike Gilbert
2017-08-14 22:24 Patrice Clement
2017-04-20 7:59 David Seifert
2016-05-27 10:22 Yixun Lan
2016-01-05 13:42 Agostino Sarubbo
2015-10-31 9:36 Ian Delaney
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=1504209174.cf2ac6788ef7314f79afacaea083f94a603ea1cc.floppym@gentoo \
--to=floppym@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