From: Giacomo Catenazzi <cate@debian.org>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: Roman Zippel <zippel@linux-m68k.org>, linux-kernel@vger.kernel.org
Subject: Re: Wanted: Volunteer to code a Patchbot
Date: Wed, 30 Jan 2002 16:32:10 +0100 [thread overview]
Message-ID: <3C5811FA.2020808@debian.org> (raw)
In-Reply-To: <fa.fphumav.16hiibk@ifi.uio.no> <fa.hqfds1v.jh2i3d@ifi.uio.no>
>
> <deleted>
> That's the problem. I have seen at least two attempted starts on a patchbot
> and know of a third (Dan Quinlan was going to do something 1.5 years ago).
> So at this point I want to step out of this discussion. There is going to
> be no patchbot without a coder to write it, so why spend more time talking
> about it?
> </deleted>
>
> OK, on a less pessimistic note, I'll make a small effort to find a volunteer
> to code this, under advisement that it will be a thankless task (everybody
> will complain about everything) and may not even get accepted by Linus or
> anyone else (yes, and?). So here it is:
>
> Wanted: a scripting person who has a clue about MTAs and wants to
> contribute to the kernel. Please step up to the table over here
> and sign in blood, then we will tell you what your mission is.
> Nobody will thank you for any of the work you do or reward you in
> any way, except for the right to bask in the glory and fame of
> being the one who ended the patchbot wars. And maybe, just maybe
> get that coveted Slashdot interview.
I can help you.
I'm good in scripting and I know well the RFC{,2}82{1,2}. (But I think
we should not worry much about these RFC.)
Wanted: a good design. I've already tried to design such bot, but I never
found a good and clean way to improve development without to change much
of current behaviour.
giacomo
next parent reply other threads:[~2002-01-30 15:32 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.fphumav.16hiibk@ifi.uio.no>
[not found] ` <fa.hqfds1v.jh2i3d@ifi.uio.no>
2002-01-30 15:32 ` Giacomo Catenazzi [this message]
2002-01-30 17:14 Wanted: Volunteer to code a Patchbot grumph
-- strict thread matches above, loose matches on Subject: below --
2002-01-30 17:14 grumph
2002-01-30 17:14 grumph
2002-01-30 17:14 grumph
2002-01-30 17:14 grumph
2002-01-30 17:14 grumph
2002-01-30 17:14 grumph
2002-01-30 17:14 grumph
2002-01-30 17:14 grumph
2002-01-30 17:14 grumph
2002-01-30 17:09 grumph
2002-01-30 17:09 grumph
2002-01-30 17:09 grumph
2002-01-30 17:09 grumph
2002-01-30 17:09 grumph
2002-01-30 17:09 grumph
2002-01-30 17:09 grumph
2002-01-30 17:09 grumph
2002-01-30 17:17 ` Daniel Phillips
2002-01-30 20:29 ` Rasmus Andersen
2002-01-31 0:41 ` Daniel Phillips
2002-01-30 19:56 ` Russell King
2002-01-31 3:09 ` Daniel Phillips
2002-01-30 17:09 grumph
2002-01-30 17:09 grumph
2002-01-30 12:39 A modest proposal -- We need a patch penguin Roman Zippel
2002-01-30 13:28 ` Wanted: Volunteer to code a Patchbot Daniel Phillips
2002-01-30 15:11 ` Rasmus Andersen
2002-01-30 15:28 ` Rasmus Andersen
2002-01-30 15:46 ` Daniel Phillips
2002-01-31 0:49 ` Stuart Young
2002-01-31 1:26 ` Daniel Phillips
2002-01-31 1:39 ` Stuart Young
2002-01-31 13:51 ` Rik van Riel
2002-01-31 15:29 ` Patrick Mauritz
2002-01-31 16:31 ` Jan Harkes
2002-01-31 22:05 ` Horst von Brand
2002-02-01 8:05 ` Daniel Phillips
2002-02-01 1:03 ` Stuart Young
2002-01-30 13:45 ` Daniel Phillips
2002-01-30 13:45 ` Tim Waugh
2002-01-30 17:46 ` Patrick Mochel
2002-01-30 18:33 ` Daniel Phillips
2002-02-03 18:54 ` Peter C. Norton
2002-02-03 23:40 ` Daniel Phillips
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=3C5811FA.2020808@debian.org \
--to=cate@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.net \
--cc=zippel@linux-m68k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.