From: "Mart Raudsepp" <leio@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libgit2-glib/
Date: Tue, 22 Aug 2017 12:59:34 +0000 (UTC) [thread overview]
Message-ID: <1503406723.0098dc9eb287b1201b710562fa53883b583161f8.leio@gentoo> (raw)
commit: 0098dc9eb287b1201b710562fa53883b583161f8
Author: Mart Raudsepp <leio <AT> gentoo <DOT> org>
AuthorDate: Tue Aug 22 12:57:57 2017 +0000
Commit: Mart Raudsepp <leio <AT> gentoo <DOT> org>
CommitDate: Tue Aug 22 12:58:43 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0098dc9e
dev-libs/libgit2-glib: enable USE=ssh by default
Most library consumers want it, and all can benefit from it
Package-Manager: Portage-2.3.6, Repoman-2.3.2
dev-libs/libgit2-glib/libgit2-glib-0.26.0-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-libs/libgit2-glib/libgit2-glib-0.26.0-r1.ebuild b/dev-libs/libgit2-glib/libgit2-glib-0.26.0-r1.ebuild
index 49d1ea552de..0697ebddf9a 100644
--- a/dev-libs/libgit2-glib/libgit2-glib-0.26.0-r1.ebuild
+++ b/dev-libs/libgit2-glib/libgit2-glib-0.26.0-r1.ebuild
@@ -14,7 +14,7 @@ LICENSE="LGPL-2+"
SLOT="0"
KEYWORDS="~amd64 ~x86"
-IUSE="python ssh +vala"
+IUSE="python +ssh +vala"
REQUIRED_USE="python? ( ${PYTHON_REQUIRED_USE} )"
# Specify libgit2 dependency with subslot because libgit2 upstream has a habit
next reply other threads:[~2017-08-22 12:59 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 12:59 Mart Raudsepp [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-21 9:24 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libgit2-glib/ Ionen Wolkens
2023-09-03 14:01 Matt Turner
2022-12-04 19:42 Matt Turner
2022-10-30 1:50 Matt Turner
2022-07-19 7:43 Michał Górny
2022-02-10 10:45 Jakov Smolić
2022-02-10 10:45 Jakov Smolić
2022-01-13 2:00 Georgy Yakovlev
2022-01-04 22:36 Georgy Yakovlev
2021-12-23 17:45 Matt Turner
2020-12-16 13:19 Michał Górny
2020-12-16 13:19 Michał Górny
2020-09-18 9:38 Michał Górny
2020-04-26 16:53 Michał Górny
2020-01-26 18:02 Mart Raudsepp
2019-08-19 4:29 Michał Górny
2019-08-18 21:51 Agostino Sarubbo
2019-08-16 22:38 Thomas Deutschmann
2019-08-15 6:29 Michał Górny
2019-07-31 11:03 Agostino Sarubbo
2019-06-08 8:00 Michał Górny
2019-05-26 11:37 Mikle Kolyada
2019-04-24 6:50 Michał Górny
2019-04-10 15:07 Michał Górny
2019-02-15 12:32 Michał Górny
2019-02-13 14:28 Michał Górny
2018-11-04 8:33 Michał Górny
2018-10-26 8:38 Michał Górny
2018-10-03 8:55 Michał Górny
2018-02-19 20:03 Mart Raudsepp
2018-02-06 18:36 Thomas Deutschmann
2018-01-26 15:03 Mikle Kolyada
2018-01-02 6:19 Michał Górny
2017-12-02 9:36 Michał Górny
2017-08-24 22:47 Gilles Dartiguelongue
2017-08-24 7:09 Michał Górny
2017-08-22 12:59 Mart Raudsepp
2017-08-13 17:03 Gilles Dartiguelongue
2017-08-13 17:03 Gilles Dartiguelongue
2017-05-05 14:51 Manuel Rüger
2017-04-18 10:56 Mart Raudsepp
2016-11-20 14:01 Manuel Rüger
2016-09-09 22:55 Gilles Dartiguelongue
2016-09-05 22:37 Gilles Dartiguelongue
2016-04-05 4:35 Alexandre Rostovtsev
2016-03-06 16:43 Mikle Kolyada
2016-03-06 3:33 Alexandre Rostovtsev
2016-03-06 3:33 Alexandre Rostovtsev
2016-02-20 13:55 Pacho Ramos
2016-02-20 13:55 Pacho Ramos
2015-12-12 14:29 Pacho Ramos
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=1503406723.0098dc9eb287b1201b710562fa53883b583161f8.leio@gentoo \
--to=leio@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