From: "David Seifert" <soap@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-vcs/rcs/
Date: Sun, 26 Nov 2017 11:39:58 +0000 (UTC) [thread overview]
Message-ID: <1511696381.a4afe6cc323a5d661ed110f6aeb11a720c079410.soap@gentoo> (raw)
commit: a4afe6cc323a5d661ed110f6aeb11a720c079410
Author: David Seifert <soap <AT> gentoo <DOT> org>
AuthorDate: Sat Nov 25 22:48:05 2017 +0000
Commit: David Seifert <soap <AT> gentoo <DOT> org>
CommitDate: Sun Nov 26 11:39:41 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a4afe6cc
dev-vcs/rcs: [QA] Consistent whitespace in metadata.xml
dev-vcs/rcs/metadata.xml | 22 +++++++++++-----------
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/dev-vcs/rcs/metadata.xml b/dev-vcs/rcs/metadata.xml
index 521535ab187..2fb1872a15b 100644
--- a/dev-vcs/rcs/metadata.xml
+++ b/dev-vcs/rcs/metadata.xml
@@ -1,15 +1,15 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
- <maintainer type="person">
- <email>titanofold@gentoo.org</email>
- <name>Aaron W. Swenson</name>
- </maintainer>
- <longdescription>
- The Revision Control System (RCS) is a system for managing
- multiple versions of files. RCS automates the storage, retrieval,
- logging, identification and merging of file revisions. RCS is useful
- for text files that are revised frequently (for example, programs,
- documentation, graphics, papers and form letters).
- </longdescription>
+ <maintainer type="person">
+ <email>titanofold@gentoo.org</email>
+ <name>Aaron W. Swenson</name>
+ </maintainer>
+ <longdescription>
+ The Revision Control System (RCS) is a system for managing
+ multiple versions of files. RCS automates the storage, retrieval,
+ logging, identification and merging of file revisions. RCS is useful
+ for text files that are revised frequently (for example, programs,
+ documentation, graphics, papers and form letters).
+ </longdescription>
</pkgmetadata>
next reply other threads:[~2017-11-26 11:40 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-26 11:39 David Seifert [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-18 2:47 [gentoo-commits] repo/gentoo:master commit in: dev-vcs/rcs/ Sam James
2022-08-02 6:52 Agostino Sarubbo
2022-08-01 8:04 Agostino Sarubbo
2022-08-01 8:03 Agostino Sarubbo
2022-08-01 8:02 Agostino Sarubbo
2022-08-01 8:02 Agostino Sarubbo
2022-08-01 8:01 Agostino Sarubbo
2022-08-01 3:27 Sam James
2022-08-01 3:24 Sam James
2022-08-01 2:33 Sam James
2022-04-22 21:47 Mike Gilbert
2022-04-14 19:28 Jakov Smolić
2022-02-03 9:40 Sam James
2021-12-09 16:23 Agostino Sarubbo
2021-12-08 23:00 Sam James
2021-12-08 6:16 Sam James
2021-12-08 6:15 Sam James
2021-12-08 6:15 Sam James
2021-12-08 6:15 Sam James
2021-12-08 6:15 Sam James
2021-10-30 17:24 Agostino Sarubbo
2021-10-30 17:22 Agostino Sarubbo
2021-10-29 18:32 Sam James
2021-10-29 18:32 Sam James
2021-10-29 18:30 Sam James
2021-10-29 18:30 Sam James
2021-10-29 18:30 Sam James
2021-01-06 22:58 Fabian Groffen
2019-12-22 12:41 David Seifert
2018-05-30 12:03 Mart Raudsepp
2016-05-29 14:19 Pacho Ramos
2015-09-21 11:27 Agostino Sarubbo
2015-09-15 4:37 Jeroen Roovers
2015-08-09 15:25 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=1511696381.a4afe6cc323a5d661ed110f6aeb11a720c079410.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