From: Michael Cummings <mcummings@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] ekeyword and ordering
Date: Tue, 7 Jun 2005 12:49:21 -0400 [thread overview]
Message-ID: <200506071249.24720.mcummings@gentoo.org> (raw)
In-Reply-To: <20050607151537.GQ9084@kaf.zko.hp.com>
[-- Attachment #1: Type: text/plain, Size: 807 bytes --]
On Tuesday 07 June 2005 11:15 am, Aron Griffis wrote:
> Diego 'Flameeyes' Pettenò wrote:[Tue Jun 07 2005, 10:20:51AM EDT]
>
> > You can't assume that maintainer arch would be x86, and with
> > alphabetic order, you must ask to the maintainer which is his arch
> > (and there's no way to learn all them by heart).
>
> or look at the ChangeLog
HA! Oh man, I needed a good chuckle. cvs log is about the only nearly reliable
thing I have found sometimes - seems folks that don't like to use
metadata.xml when commiting a random package also avoid using ChangeLogs. Go
figure.
--
-----o()o---------------------------------------------
Michael Cummings | #gentoo-dev, #gentoo-perl
Gentoo Perl Dev | on irc.freenode.net
-----o()o---------------------------------------------
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-06-07 16:49 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 22:26 [gentoo-dev] ekeyword and ordering Aron Griffis
2005-06-06 22:41 ` Mike Frysinger
2005-06-06 22:49 ` Stephen P. Becker
2005-06-07 12:16 ` Luca Barbato
2005-06-07 20:58 ` Danny van Dyk
2005-06-09 13:19 ` foser
2005-06-09 13:37 ` Lars Weiler
2005-06-09 15:59 ` [gentoo-dev] " Duncan
2005-06-09 15:29 ` [gentoo-dev] " Danny van Dyk
2005-06-09 15:50 ` Stephen P. Becker
2005-06-10 14:55 ` foser
2005-06-10 16:33 ` Mike Frysinger
2005-06-11 8:15 ` foser
2005-06-11 8:28 ` Jason Stubbs
2005-06-11 8:48 ` foser
2005-06-11 15:21 ` Joshua Baergen
2005-06-11 16:31 ` Diego 'Flameeyes' Pettenò
2005-06-11 18:00 ` Joshua Baergen
2005-06-11 9:06 ` Bryan Oestergaard
2005-06-11 18:46 ` Aron Griffis
2005-08-01 17:06 ` foser
2005-08-01 17:43 ` Aron Griffis
2005-06-11 20:37 ` Mike Frysinger
2005-06-10 17:19 ` Aron Griffis
2005-06-11 0:04 ` Georgi Georgiev
2005-06-11 12:48 ` Aron Griffis
2005-06-12 0:39 ` Georgi Georgiev
2005-06-12 2:18 ` Aron Griffis
2005-06-06 22:43 ` [gentoo-dev] " Michael Sterrett -Mr. Bones.-
2005-06-09 13:06 ` foser
2005-06-06 22:47 ` [gentoo-dev] " Lars Weiler
2005-06-07 3:19 ` Aaron Walker
2005-06-07 18:35 ` Donnie Berkholz
2005-06-09 13:10 ` foser
2005-06-09 16:49 ` Maurice van der Pot
2005-06-07 11:23 ` Simon Stelling
2005-06-07 14:04 ` Aron Griffis
2005-06-07 14:20 ` Diego 'Flameeyes' Pettenò
2005-06-07 15:15 ` Aron Griffis
2005-06-07 15:30 ` Diego 'Flameeyes' Pettenò
2005-06-07 22:35 ` Chris Gianelloni
2005-06-07 16:49 ` Michael Cummings [this message]
2005-06-07 18:38 ` Aron Griffis
2005-06-07 22:31 ` Chris Gianelloni
2005-06-07 22:32 ` Diego 'Flameeyes' Pettenò
2005-06-07 21:32 ` Marcus D. Hanwell
2005-06-07 21:44 ` Aron Griffis
2005-06-07 21:56 ` Olivier Crete
2005-06-07 22:11 ` Marcus D. Hanwell
2005-06-07 23:58 ` Lars Weiler
2005-06-07 22:18 ` Aron Griffis
2005-06-09 13:01 ` foser
2005-06-08 14:44 ` Jason Wever
2005-06-08 15:39 ` Joseph Jezak
2005-06-08 16:18 ` Marcus D. Hanwell
2005-06-08 16:23 ` Jason Wever
2005-06-07 23:07 ` Ferris McCormick
2005-06-08 0:25 ` Donnie Berkholz
2005-06-08 13:15 ` Chris Gianelloni
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=200506071249.24720.mcummings@gentoo.org \
--to=mcummings@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