From: "Michael Haubenwallner" <haubi@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: profiles/prefix/
Date: Mon, 10 Apr 2017 12:28:10 +0000 (UTC) [thread overview]
Message-ID: <1491827275.d63ddb3e23f31eb6320f96e51c50cfbbb7389042.haubi@gentoo> (raw)
commit: d63ddb3e23f31eb6320f96e51c50cfbbb7389042
Author: Michael Haubenwallner <haubi <AT> gentoo <DOT> org>
AuthorDate: Mon Apr 10 12:27:55 2017 +0000
Commit: Michael Haubenwallner <haubi <AT> gentoo <DOT> org>
CommitDate: Mon Apr 10 12:27:55 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d63ddb3e
profiles/prefix: p.use.mask python_targets_python3_4
profiles/prefix/use.mask | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/profiles/prefix/use.mask b/profiles/prefix/use.mask
index 58031ae9505..4826702151b 100644
--- a/profiles/prefix/use.mask
+++ b/profiles/prefix/use.mask
@@ -9,3 +9,7 @@ kernel_linux
# and Gentoo Prefix does not have access to that. Also, definately problems with
# coreutils on darwin.
acl
+
+# app-editors/vim does not like multiple python3 targets (bug#575096),
+# but PYTHON_TARGETS=-python3_4 does not work either (is not incremental).
+python_targets_python3_4
next reply other threads:[~2017-04-10 12:28 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 12:28 Michael Haubenwallner [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-11 10:28 [gentoo-commits] repo/gentoo:master commit in: profiles/prefix/ Sam James
2024-08-07 6:23 Fabian Groffen
2023-11-25 5:46 Sam James
2023-06-24 18:36 Fabian Groffen
2023-06-24 13:25 Fabian Groffen
2023-04-30 7:26 Sam James
2021-08-24 11:33 Fabian Groffen
2021-08-23 17:22 Fabian Groffen
2021-03-13 13:09 Fabian Groffen
2021-01-23 11:32 Fabian Groffen
2021-01-14 18:58 Sam James
2021-01-02 14:31 Fabian Groffen
2021-01-02 14:29 Fabian Groffen
2020-12-10 20:18 Sam James
2020-08-18 18:35 Fabian Groffen
2020-08-02 8:02 Fabian Groffen
2020-08-02 7:57 Fabian Groffen
2020-07-24 18:58 Fabian Groffen
2020-06-07 11:34 Fabian Groffen
2020-06-05 18:02 Fabian Groffen
2020-03-26 7:15 Fabian Groffen
2019-05-31 9:15 Fabian Groffen
2019-03-01 11:10 Michael Haubenwallner
2018-12-29 13:03 Fabian Groffen
2018-12-27 19:09 Fabian Groffen
2018-12-27 18:48 Fabian Groffen
2018-07-18 8:33 Fabian Groffen
2018-06-23 23:22 Mikle Kolyada
2018-06-22 12:00 Michał Górny
2018-06-21 10:54 Michael Haubenwallner
2018-06-20 11:16 Michael Haubenwallner
2018-06-20 8:12 Fabian Groffen
2018-06-20 8:12 Fabian Groffen
2018-01-31 10:23 Fabian Groffen
2017-09-12 11:02 Fabian Groffen
2017-08-22 12:24 Michael Haubenwallner
2017-06-21 11:34 Fabian Groffen
2017-06-21 9:29 Fabian Groffen
2017-06-21 8:10 Fabian Groffen
2017-04-15 8:37 Fabian Groffen
2017-04-05 14:12 Michael Haubenwallner
2017-04-03 15:36 Michael Haubenwallner
2017-02-23 14:32 Michał Górny
2016-06-27 16:09 Fabian Groffen
2016-06-01 18:54 Fabian Groffen
2016-03-04 17:22 Fabian Groffen
2016-02-20 14:06 Fabian Groffen
2016-02-17 14:44 Fabian Groffen
2016-01-30 20:49 Fabian Groffen
2016-01-21 18:20 Fabian Groffen
2016-01-21 18:05 Fabian Groffen
2016-01-21 13:46 Fabian Groffen
2016-01-11 19:16 Fabian Groffen
2016-01-11 18:04 Fabian Groffen
2016-01-06 19:43 Fabian Groffen
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=1491827275.d63ddb3e23f31eb6320f96e51c50cfbbb7389042.haubi@gentoo \
--to=haubi@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