From: "Virgil Dupras" <vdupras@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libsass/
Date: Fri, 5 Jul 2019 19:05:14 +0000 (UTC) [thread overview]
Message-ID: <1562353257.128798305d9a4c573c49b58cd3808ae431a90858.vdupras@gentoo> (raw)
commit: 128798305d9a4c573c49b58cd3808ae431a90858
Author: Virgil Dupras <vdupras <AT> gentoo <DOT> org>
AuthorDate: Fri Jul 5 19:00:57 2019 +0000
Commit: Virgil Dupras <vdupras <AT> gentoo <DOT> org>
CommitDate: Fri Jul 5 19:00:57 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=12879830
dev-libs/libsass: remove myself as maintainer
Signed-off-by: Virgil Dupras <vdupras <AT> gentoo.org>
Package-Manager: Portage-2.3.66, Repoman-2.3.11
dev-libs/libsass/metadata.xml | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/dev-libs/libsass/metadata.xml b/dev-libs/libsass/metadata.xml
index 58b843a9d6a..191514e5850 100644
--- a/dev-libs/libsass/metadata.xml
+++ b/dev-libs/libsass/metadata.xml
@@ -1,10 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
- <maintainer type="person">
- <email>vdupras@gentoo.org</email>
- <name>Virgil Dupras</name>
- </maintainer>
+ <!-- maintainer-needed -->
<longdescription lang="en">
LibSass is a C++ port of the original Ruby Sass CSS compiler with a C
API. It is coded with portability and efficiency in mind. You can
next reply other threads:[~2019-07-05 19:05 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 19:05 Virgil Dupras [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-31 13:11 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libsass/ Nowa Ammerlaan
2024-12-04 9:15 Sam James
2024-12-02 13:15 Jakov Smolić
2024-12-01 19:57 Arthur Zamarin
2024-12-01 19:07 Arthur Zamarin
2024-12-01 19:02 Arthur Zamarin
2024-12-01 19:02 Arthur Zamarin
2023-12-23 9:52 Andrew Ammerlaan
2023-04-07 18:25 Sam James
2022-12-18 9:27 Sam James
2022-12-18 9:27 Sam James
2022-09-09 7:59 David Seifert
2022-06-28 4:18 WANG Xuerui
2022-06-19 8:14 Agostino Sarubbo
2021-11-01 15:46 Sam James
2021-05-22 15:31 Andrew Ammerlaan
2021-05-22 15:10 Sam James
2021-05-22 3:05 Sam James
2021-05-22 1:32 Sam James
2021-05-21 14:02 Andrew Ammerlaan
2021-05-21 7:57 Michał Górny
2020-05-02 11:55 James Le Cuirot
2020-05-02 11:55 James Le Cuirot
2020-03-06 15:55 Joonas Niilola
2020-01-27 19:53 Mart Raudsepp
2020-01-07 4:08 Joonas Niilola
2019-11-19 15:40 Agostino Sarubbo
2019-11-19 7:38 Agostino Sarubbo
2019-11-19 1:31 Aaron Bauman
2019-08-20 4:44 Hans de Graaff
2019-05-28 2:35 Aaron Bauman
2019-05-19 21:41 Virgil Dupras
2019-05-19 21:41 Virgil Dupras
2019-05-18 12:28 Virgil Dupras
2019-03-30 0:12 Virgil Dupras
2019-03-24 10:01 Agostino Sarubbo
2019-03-02 19:56 Sergei Trofimovich
2019-02-19 18:04 Andreas Sturmlechner
2018-10-23 22:43 James Le Cuirot
2018-03-23 20:17 Alexandre Rostovtsev
2018-01-29 3:17 Alexandre Rostovtsev
2017-12-28 15:20 Alexandre Rostovtsev
2017-12-28 15:20 Alexandre Rostovtsev
2017-12-26 2:06 Thomas Deutschmann
2017-11-23 18:43 Alexandre Rostovtsev
2017-11-13 21:36 Alexandre Rostovtsev
2017-11-07 8:41 Alexandre Rostovtsev
2017-11-07 8:37 Alexandre Rostovtsev
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=1562353257.128798305d9a4c573c49b58cd3808ae431a90858.vdupras@gentoo \
--to=vdupras@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