From: Rusty Russell <rusty@rustcorp.com.au>
To: Pavel Machek <pavel@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Centenary Reached By Trivial Patch Monkey
Date: Fri, 31 May 2002 12:32:02 +1000 [thread overview]
Message-ID: <E17DcCw-0006tk-00@wagner.rustcorp.com.au> (raw)
In-Reply-To: Your message of "Thu, 30 May 2002 00:27:06 GMT." <20020530002705.B155@toy.ucw.cz>
In message <20020530002705.B155@toy.ucw.cz> you write:
> Hi!
>
> > 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).
>
> Just -- thanks for that. "Patch and forget" is very welcome for easy patches.
Yes, this was in fact my motiviation: it takes about 30 seconds to do
a one-liner patch when you're reading through code. It's not much
extra effort to gather everyone else's as well...
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
prev parent reply other threads:[~2002-05-31 2:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-29 3:38 Centenary Reached By Trivial Patch Monkey Rusty Russell
2002-05-29 14:14 ` Eli Carter
2002-05-30 0:27 ` Pavel Machek
2002-05-31 2:32 ` Rusty Russell [this message]
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=E17DcCw-0006tk-00@wagner.rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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