From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Ebuild bumping policy wrt KEYWORDS
Date: Thu, 26 Aug 2004 16:33:26 +0100 [thread overview]
Message-ID: <20040826163326.5bd1e08d@snowdrop.home> (raw)
In-Reply-To: <200408261730.11098.carlo@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]
On Thu, 26 Aug 2004 17:30:11 +0200 Carsten Lohrke <carlo@gentoo.org>
wrote:
| On Thursday 26 August 2004 17:04, Ciaran McCreesh wrote:
| > Personally I prefer my original wording:
| > > Arch teams: when moving from ~arch to arch on an actively
| > > maintained package where you're going ahead of the maintainer's
| > > arch, it's best to consult first. You don't necessarily have to
| > > follow the maintainer's advice, but at least listen to what they
| > > have to say.
|
| The problem is still the same: Other arch maintainers can't know,
| which arch is the package maintainers arch. I would always deny or
| mask it stable on my arch as well, if I had no objections.
*sigh* x86 having broken stable gnome for two weeks and not realising
it (whilst other archs who went ahead of x86 had it working) just goes
to show that this is not always the case.
Oh, and you're assuming that all your packages are entirely arch
neutral. This is also not always the case.
--
Ciaran McCreesh : Gentoo Developer (Sparc, MIPS, Vim, Fluxbox)
Mail : ciaranm at gentoo.org
Web : http://dev.gentoo.org/~ciaranm
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-08-26 15:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 1:11 [gentoo-dev] Ebuild bumping policy wrt KEYWORDS Jason Wever
2004-08-25 3:00 ` Jason Wever
2004-08-25 15:30 ` Michael Kohl
2004-08-26 3:17 ` Jason Wever
2004-08-26 14:51 ` Carsten Lohrke
2004-08-26 15:04 ` Ciaran McCreesh
2004-08-26 15:30 ` Carsten Lohrke
2004-08-26 15:33 ` Ciaran McCreesh [this message]
2004-08-26 16:11 ` Travis Tilley
2004-08-31 13:07 ` foser
2004-09-01 2:09 ` Travis Tilley
2004-09-01 10:06 ` foser
2004-09-01 16:30 ` Robert Moss
2004-09-01 23:15 ` Carsten Lohrke
2004-09-01 23:20 ` Ciaran McCreesh
2004-09-01 23:42 ` Carsten Lohrke
2004-08-26 16:27 ` Carsten Lohrke
2004-08-31 13:23 ` foser
2004-08-25 13:51 ` Chris Gianelloni
2004-08-26 3:22 ` Jason Wever
2004-08-26 4:49 ` Donnie Berkholz
2004-08-26 5:20 ` Jason Wever
2004-08-26 6:19 ` Donnie Berkholz
2004-08-26 14:16 ` Chris Gianelloni
2004-08-26 14:44 ` Ciaran McCreesh
2004-08-26 15:02 ` Chris Gianelloni
2004-08-26 15:31 ` Jason Wever
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=20040826163326.5bd1e08d@snowdrop.home \
--to=ciaranm@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