mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: linux-kernel@vger.kernel.org
Subject: Centenary Reached By Trivial Patch Monkey
Date: Wed, 29 May 2002 13:38:52 +1000	[thread overview]
Message-ID: <E17CuIW-0006BC-00@wagner.rustcorp.com.au> (raw)

Hi All,

	With the recent flurry of inclusions, the trivial@
rustcorp.com.au Trivial Patch Monkey has passed 100 patches which have
filtered into the various kernels: 5 into 2.2, 55 into 2.4 and 71 into
2.5.  Linus and Marcelo now seem well trained to take the patches
(although the bogus attribution is a problem).

	With this surprising success (I thought the damn thing would
die after a few days), I will be continuing to provide the service,
which only takes me about an hour a week.

Usage notes:
	1) Please provide one patch per email, even if it means 50
	   emails.

	2) Make sure your diffs are -p1 compliant, ie:
		+++ linux/drivers/net/foo.c

	3) MIME is fine.

	4) CC'ing trivial is fine: I usually only forward the patch
	   if a kernel has been released since.

	5) I actually read the patches, so don't expect real-time
	   response.

FYI, most patches are: (1) janitorial fixes from new people who can't
get Linus or linux-kernel to read their patches (aka. Alan Cox Mode),
and (2) one-liners from experienced kernel hackers who wouldn't bother
retransmitting themselves (aka. Drop Prevention Mode).

Thanks!
Trivial Patch Monkey.
--
  Oook ook! Chirp Eep? *THWACK*
	-- Sound of 30 trivial patches hitting penguin 

             reply	other threads:[~2002-05-29  3:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-29  3:38 Rusty Russell [this message]
2002-05-29 14:14 ` Eli Carter
2002-05-30  0:27 ` Pavel Machek
2002-05-31  2:32   ` Rusty Russell

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=E17CuIW-0006BC-00@wagner.rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®