From: Alin Nastac <mrness@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] Please follow keywording policy
Date: Wed, 09 Mar 2005 19:40:51 +0200 [thread overview]
Message-ID: <422F3523.2000902@gentoo.org> (raw)
In-Reply-To: <1110386590.9520.260.camel@cgianelloni.nuvox.net>
[-- Attachment #1: Type: text/plain, Size: 1364 bytes --]
Chris Gianelloni wrote:
>On Wed, 2005-03-09 at 09:38 +0200, Alin Nastac wrote:
>
>
>>I think the reason people drop arches is laziness of some arch herds.
>>C'mon people, how hard can it be to see if it builds right on your arch?
>>
>>
>
>What arch do you use? Maybe we should trade in your box for a nice
>sparc32 or mips box and see what you have to say then. Remember that in
>many of these arches, all the machines are still measured in Megahertz
>and not Gigahertz, and they are quite old.
>
>The arch teams are doing their jobs quite well, don't try to push blame
>onto them. They shouldn't go around marking something stable just
>because it builds and should test it. If they have no way of testing
>it, then they don't need to stabilize it. It won't kill you to have a
>single older ebuild in the tree for an arch. Either that, or you can
>remove the keywords, as Jason mentioned, and file a bug against the
>package to the mips team so they are aware that keywords have been
>dropped from the package and that it will need testing to be
>re-keyworded. Looking over that bug, it really looks like you flipped
>out over nothing. It took them a week to respond. That isn't very
>long, at all.
>
>
Hmm.. it looks like I've overreacted. I was convinced that my request
have been ignored for one month.
My apologies to mips team and all...
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
prev parent reply other threads:[~2005-03-09 17:40 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 1:55 [gentoo-dev] Please follow keywording policy Jason Wever
2005-03-09 2:00 ` Hasan Khalil
2005-03-09 7:38 ` Alin Nastac
2005-03-09 13:39 ` Stephen P. Becker
2005-03-09 14:50 ` Alin Nastac
2005-03-09 16:22 ` Ciaran McCreesh
2005-03-09 17:38 ` Alin Nastac
2005-03-09 18:38 ` Ciaran McCreesh
2005-03-09 18:56 ` Alin Nastac
2005-03-09 19:10 ` Stefan Schweizer
2005-03-09 19:10 ` Stefan Schweizer
2005-03-09 21:30 ` Luis F. Araujo
2005-03-09 22:57 ` Alin Nastac
2005-03-09 23:27 ` Stephen P. Becker
2005-03-10 0:50 ` Donnie Berkholz
2005-03-10 0:18 ` Daniel Goller
2005-03-09 23:36 ` Jason Wever
2005-03-09 23:42 ` Aron Griffis
2005-03-10 7:54 ` Alin Nastac
2005-03-10 8:27 ` Ciaran McCreesh
2005-03-10 15:54 ` Chris Gianelloni
2005-03-10 15:52 ` Chris Gianelloni
2005-03-10 4:34 ` Grant Goodyear
2005-03-10 8:36 ` Alin Nastac
2005-03-10 13:14 ` Ciaran McCreesh
2005-03-10 16:00 ` Chris Gianelloni
2005-03-10 19:00 ` Alin Nastac
2005-03-10 19:33 ` Chris Gianelloni
2005-03-10 21:25 ` John Myers
2005-03-10 15:38 ` Chris Gianelloni
2005-03-09 19:18 ` Patrick Lauer
2005-03-09 19:43 ` Stefan Schweizer
2005-03-09 19:56 ` Patrick Lauer
2005-03-10 0:55 ` Jon Portnoy
2005-03-10 8:07 ` Alin Nastac
2005-03-09 19:20 ` Chris Gianelloni
2005-03-09 16:37 ` Stephen P. Becker
2005-03-09 16:43 ` Chris Gianelloni
2005-03-09 17:40 ` Alin Nastac [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=422F3523.2000902@gentoo.org \
--to=mrness@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.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