public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: Proposal for how to handle stable ebuilds
Date: Tue, 18 Nov 2008 16:45:04 -0600	[thread overview]
Message-ID: <20081118164504.466dff16@halo.dirtyepic.sk.ca> (raw)
In-Reply-To: 1227045873.4891.79.camel@athena.ghs.com

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

On Tue, 18 Nov 2008 17:04:33 -0500
Daniel Gryniewicz <dang@gentoo.org> wrote:

> Honestly, I don't want to be a dick to the arch teams.  I really
> don't. But I *also* don't want them (or policy) to be a dick to me.
> That's my whole point; that requirement of never removing the last
> stable ebuild, in shouting caps no less, is way too absolute, and is
> just going to piss people like me off.

For the record, the all in caps bit was a tongue-in-cheek reference to
the ultra-formal format that the IETF RFC's are in that was being
emulated here.  It was included for levity, not for shouting.

http://www.rfc-editor.org/rfc/rfc2119.txt


-- 
gcc-porting,                                      by design, by neglect
treecleaner,                              for a fact or just for effect
wxwidgets @ gentoo     EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-11-18 22:45 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-10 18:13 [gentoo-dev] Proposal for how to handle stable ebuilds Mark Loeser
2008-11-10 18:23 ` Ciaran McCreesh
2008-11-10 18:23 ` Mart Raudsepp
2008-11-10 20:32   ` Steev Klimaszewski
2008-11-10 21:16 ` Jeremy Olexa
2008-11-10 21:57 ` Santiago M. Mola
2008-11-11  0:24 ` Jose Luis Rivero
2008-11-11  1:13   ` Mark Loeser
2008-11-11  9:31     ` Jose Luis Rivero
2008-11-11  1:21   ` Richard Freeman
2008-11-11  8:56     ` Peter Volkov
2008-11-11 10:18     ` Jose Luis Rivero
2008-11-11 13:49       ` Ferris McCormick
2008-11-11 16:06       ` [gentoo-dev] " Duncan
2008-11-11 16:24         ` Jeroen Roovers
2008-11-11 17:26           ` Duncan
2008-11-11 17:55             ` Ferris McCormick
2008-11-11 18:12             ` Jeroen Roovers
2008-11-11 21:03               ` Duncan
2008-11-13 17:38 ` [gentoo-dev] " Tobias Scherbaum
2008-11-15 13:02   ` Matti Bickel
2008-11-17 18:08     ` Tobias Scherbaum
2008-11-17 19:03       ` [gentoo-dev] " Duncan
2008-12-11  5:35       ` [gentoo-dev] " Donnie Berkholz
2008-11-17  0:38 ` [gentoo-dev] " Ryan Hill
2008-11-17 15:10   ` Daniel Gryniewicz
2008-11-18  1:08     ` Ryan Hill
2008-11-18 16:57       ` Daniel Gryniewicz
2008-11-18 17:50         ` Ciaran McCreesh
2008-11-18 20:31           ` Daniel Gryniewicz
2008-11-18 21:18         ` Ryan Hill
2008-11-18 22:04           ` Daniel Gryniewicz
2008-11-18 22:45             ` Ryan Hill [this message]
2008-11-30 22:59 ` Ryan Hill
2008-12-01  7:49   ` Peter Volkov
2008-12-11  5:37 ` [gentoo-dev] " Donnie Berkholz

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=20081118164504.466dff16@halo.dirtyepic.sk.ca \
    --to=dirtyepic@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