From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: For Jakub (and the other procmail-impaired)
Date: Tue, 17 Jul 2007 12:02:38 -0700 [thread overview]
Message-ID: <1184698958.8603.11.camel@inertia.twi-31o2.org> (raw)
In-Reply-To: <f7h794$dsd$1@sea.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 738 bytes --]
On Tue, 2007-07-17 at 02:52 +0100, Steve Long wrote:
> Perhaps you'd like to explain just how Mr Gianelloni's post was NOT a troll
> then? Or is every developer's procmail setting (particularly for such a
> stupid thread) a matter we should all be discussing? It's not like amne
> never pointed out, several mails ago, that the whole thread had been done
> to death or anything, is it?
>
> And no, I don't like being lumped in with Mr McCreesh.
How exactly is the technical answer to a technical question (from Jakub,
about how to avoid the thread) a troll?
--
Chris Gianelloni
Release Engineering Strategic Lead
Alpha/AMD64/x86 Architecture Teams
Games Developer/Council Member/Foundation Trustee
Gentoo Foundation
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-07-17 19:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 22:29 [gentoo-dev] For Jakub (and the other procmail-impaired) Chris Gianelloni
2007-07-17 0:30 ` [gentoo-dev] " Steve Long
2007-07-17 0:59 ` Ryan Hill
2007-07-17 1:52 ` Steve Long
2007-07-17 2:05 ` George Prowse
2007-07-17 2:06 ` George Prowse
2007-07-17 2:49 ` Vlastimil Babka
2007-07-17 6:47 ` [gentoo-dev] alternative solution for 'procmail-impaired' folks Jakub Moc
2007-07-17 19:02 ` Chris Gianelloni [this message]
2007-07-17 7:07 ` [gentoo-dev] Re: For Jakub (and the other procmail-impaired) Ned Ludd
2007-07-17 11:49 ` Samuli Suominen
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=1184698958.8603.11.camel@inertia.twi-31o2.org \
--to=wolf31o2@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