From: Tomas Szepe <szepe@pinerecords.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: some kernel config menu suggested tweaks
Date: Sat, 26 Jul 2003 15:01:42 +0200 [thread overview]
Message-ID: <20030726130142.GD6560@louise.pinerecords.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0307260821570.30928@localhost.localdomain>
> > Send a patch.
>
> i'd be happy to, but based on my previous experience sending
> in a few patches, it's just not worth the aggravation any more.
Well, you know the Gandhi routine: Whatever you do will be
insignificant, but it is very important that you do it.
> just one of my patches that got adopted took, literally, several
> weeks of being dropped on the floor with no reason why.
Trivial patches need to go to people like AC who tend to focus
on aggregating fixes and are in a much better position to push
upstream.
> "we can't hire you. you don't have enough experience doing
> this job."
> "ok, so how do i get experience?"
> "well, you have to do this job for a while."
At which point you must get yossarian-ish enough to start a company.
--
Tomas Szepe <szepe@pinerecords.com>
next prev parent reply other threads:[~2003-07-26 12:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-24 17:05 some kernel config menu suggested tweaks Robert P. J. Day
2003-07-26 12:14 ` Tomas Szepe
2003-07-26 12:30 ` Robert P. J. Day
2003-07-26 13:01 ` Tomas Szepe [this message]
2003-07-26 13:45 ` Randy.Dunlap
2003-07-24 18:45 John Bradford
2003-07-24 18:49 ` Robert P. J. Day
2003-07-24 19:10 John Bradford
2003-07-24 19:53 ` Petr Vandrovec
2003-07-26 12:52 ` Tomas Szepe
2003-07-26 13:07 ` Robert P. J. Day
2003-07-26 14:33 ` Tomas Szepe
2003-07-26 15:20 John Bradford
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=20030726130142.GD6560@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.com \
/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;
as well as URLs for NNTP newsgroup(s).