From: Aaron Bauman <bman@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Deprecating AMD64 17.0 profiles?
Date: Mon, 09 Nov 2020 07:48:42 -0500 [thread overview]
Message-ID: <50E745B2-CA69-44BD-B85C-36DD67E191CC@gentoo.org> (raw)
In-Reply-To: <20201109115433.32278.qmail@stuge.se>
On November 9, 2020 6:54:33 AM EST, Peter Stuge <peter@stuge.se> wrote:
>Andreas K. Hüttel wrote:
>> it's probably time to deprecate the amd64 17.0 profiles!
>
>I for one am not so excited about the amd64 17.1 profiles. On the
>surface
>it appeared to me that one developer has "taken over" just about
>everything,
>which (regardless of the individual) can't be a good thing..
>
What does this even mean?
>
>Jaco Kroon wrote:
>> ...just wondering where the lib32 => lib symlink comes from now.
>
>baselayout contains a conversion to/from lib symlink(s).
>
>
>Kind regards
>
>//Peter
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2020-11-09 12:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 15:17 [gentoo-dev] [PATCH] profiles: Reorder AMD64 profile list to place 17.1 on top Brian Evans
2020-10-22 15:44 ` Michał Górny
2020-10-22 19:16 ` [gentoo-dev] Deprecating AMD64 17.0 profiles? Andreas K. Hüttel
2020-11-07 11:42 ` Alexey Sokolov
2020-11-07 11:56 ` Fabian Groffen
2020-11-09 19:38 ` Alexey Sokolov
2020-11-10 7:55 ` Fabian Groffen
2020-11-10 8:34 ` Michał Górny
2020-11-10 8:41 ` Fabian Groffen
2020-11-10 8:49 ` Michał Górny
2020-11-10 8:53 ` Fabian Groffen
2020-11-10 9:13 ` Michał Górny
2020-11-10 9:21 ` Alexey Sokolov
2020-11-10 9:27 ` Fabian Groffen
2020-11-07 13:39 ` Andreas K. Huettel
2020-11-07 14:01 ` Alexey Sokolov
2020-11-09 10:30 ` Jaco Kroon
2020-11-09 10:59 ` Ulrich Mueller
2020-11-09 11:09 ` Jaco Kroon
2020-11-09 11:45 ` Marek Szuba
2020-11-09 11:54 ` Peter Stuge
2020-11-09 12:48 ` Aaron Bauman [this message]
2020-11-09 12:57 ` Andreas K. Huettel
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=50E745B2-CA69-44BD-B85C-36DD67E191CC@gentoo.org \
--to=bman@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