public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Steve Long <slong@rathaus.eclipse.co.uk>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: For Jakub (and the other procmail-impaired)
Date: Tue, 17 Jul 2007 02:52:46 +0100	[thread overview]
Message-ID: <f7h794$dsd$1@sea.gmane.org> (raw)
In-Reply-To: f7h49j$7ld$1@sea.gmane.org

Ryan Hill wrote:

> Steve Long wrote:
>> Chris Gianelloni wrote:
>> 
>>> :0
>>> * ^List-Id:.gentoo-dev.gentoo.org.
>>> * ^Subject:.*ML changes
>>> /dev/null
>>>
>> Sorry was there some reason the rest of us had to read this? If so,
>> please explain it like a responsible Council member. Or is this your
>> swansong? If so it's l4m3.
> 
> Please stop blatantly trolling.  It will not be tolerated on this list.
> 
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.


-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2007-07-17  1:53 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 [this message]
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       ` [gentoo-dev] Re: For Jakub (and the other procmail-impaired) Chris Gianelloni
2007-07-17  7:07   ` 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='f7h794$dsd$1@sea.gmane.org' \
    --to=slong@rathaus.eclipse.co.uk \
    --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