public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org, gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-dev] arches.desc & GLEP 72 (was: Re: [gentoo-project] Items for Council Agenda, May 14)
Date: Sat, 06 May 2017 18:35:08 +0200	[thread overview]
Message-ID: <1494088508.26467.1.camel@gentoo.org> (raw)
In-Reply-To: <2845173.ZUnlo4BlrU@pinacolada>

[-- Attachment #1: Type: text/plain, Size: 1495 bytes --]

On sob, 2017-05-06 at 16:34 +0200, Andreas K. Huettel wrote:
> Am Samstag, 29. April 2017, 19:00:34 CEST schrieb Anthony G. Basile:
> > Hi everyone,
> > 
> > The Gentoo Council will be meeting in two weeks.  If anyone has any
> > issues we need to discuss, please let me know and I'll put it on the
> > agenda.  Thanks.
> 
> I've converted the arches.desc proposal into a GLEP, taking (some of) the 
> mailing list comments into account.
> 
> https://wiki.gentoo.org/wiki/GLEP:72
> https://wiki.gentoo.org/wiki/User:Dilfridge/GLEP:72
> 
> (the texts are identical at the moment, but if there are additional comments I 
> can more easily adapt the version in my user space).
> 
> I would like the council to talk about it and potentially give it a go-ahead. 
> 
> An implementation is still missing though.
> 

...and a rationale section to describe why you did the things this way.

Few notes:

1. I think your example is a bit misleading -- unless I'm missing
something, mips would be 'unstable' right now, and m68k would be
'testing'.

2. I can't say I like using magical keywords like 'testing'
and 'unstable'; they're going to be confusing long-term (compare:
the mess with stable/exp/dev for profiles). But I don't have a very good
idea how to it better right now.

3. What is the use case for 'broken'? Are we ever going to use that?

Plus, you have a few typos, you need to wikify it and other minor blah
blah.

-- 
Best regards,
Michał Górny

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 963 bytes --]

      reply	other threads:[~2017-05-06 16:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0ac908a7-9875-f629-fa0c-0c85945e1185@gentoo.org>
2017-05-06 14:34 ` [gentoo-dev] arches.desc & GLEP 72 (was: Re: [gentoo-project] Items for Council Agenda, May 14) Andreas K. Huettel
2017-05-06 16:35   ` Michał Górny [this message]

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=1494088508.26467.1.camel@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gentoo-project@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