public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: 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 19:36:42 +0200	[thread overview]
Message-ID: <2792793.3ddXxQ3v2e@pinacolada> (raw)
In-Reply-To: <1494088508.26467.1.camel@gentoo.org>

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

Am Samstag, 6. Mai 2017, 18:35:08 CEST schrieb Michał Górny:
>
> > An implementation is still missing though.
> 
> ...and a rationale section to describe why you did the things this way.

Well, that's more or less the Motivation section. Should I rename it?

> 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'.

Right. Fixed. 

> 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.

Well, I pulled the two terms that are tradidionally used for ~arch... 
"testing" and "unstable". Testing implied to me that a transition is taking 
place, so that went to the "mixed state". 

There's also Kent's proposal where some more indirection is introduced (see 
the discussion threads). It more or less achives the same with even more 
flexibility. I dont like it so much because I want to keep things simple.

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

None that I know of. I only added it because it was suggested on the list (and 
because it's simple to define and implement).

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


-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer (council, perl, libreoffice)

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

  reply	other threads:[~2017-05-06 17:36 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-29 17:00 [gentoo-project] Items for Council Agenda, May 14 Anthony G. Basile
2017-04-30 13:52 ` Andreas K. Huettel
2017-05-03 21:26   ` Daniel Campbell
2017-05-06 14:34 ` arches.desc & GLEP 72 (was: Re: [gentoo-project] Items for Council Agenda, May 14) Andreas K. Huettel
2017-05-06 16:35   ` [gentoo-dev] " Michał Górny
2017-05-06 17:36     ` Andreas K. Huettel [this message]
2017-05-06 20:23       ` Michał Górny
2017-05-07  2:53         ` Kent Fredric
2017-05-07 20:30       ` Michał Górny
2017-05-08 11:46         ` Andreas K. Huettel
2017-05-13  0:03     ` Andreas K. Huettel
2017-05-13  7:44       ` Michał Górny
2017-05-13 22:48         ` Andreas K. Huettel
2017-05-07 15:47   ` Roy Bamford
2017-05-14 15:38     ` Andreas K. Huettel
2017-05-11  7:17 ` [gentoo-project] Items for Council Agenda, May 14 Matthias Maier
2017-05-11  7:52   ` NP-Hardass
2017-05-11  8:02     ` Michał Górny
2017-05-11  9:16       ` Raymond Jennings
2017-05-11 10:08   ` Kent Fredric
2017-05-11 10:52     ` Rich Freeman
2017-05-11 15:03       ` Gregory Woodbury
2017-05-11 16:45   ` Luis Ressel
2017-05-11 19:57     ` Rich Freeman
2017-05-11 20:24       ` William L. Thomson Jr.
2017-05-11 20:28       ` Michał Górny
2017-05-13  9:26       ` Kent Fredric
2017-05-14  1:46         ` M. J. Everitt
2017-05-11 18:55   ` Roy Bamford
2017-05-11 19:09     ` Raymond Jennings
2017-05-11 19:54       ` Rich Freeman
2017-05-13  9:14       ` Kent Fredric
2017-05-11 20:25   ` William L. Thomson Jr.
2017-05-11 23:07   ` Daniel Campbell
2017-05-12  8:52     ` Roy Bamford
2017-05-12 10:41       ` Andreas K. Huettel
2017-05-13  9:36         ` Daniel Campbell

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=2792793.3ddXxQ3v2e@pinacolada \
    --to=dilfridge@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