From: "jdow" <jdow@earthlink.net>
To: "David S. Miller" <davem@redhat.com>,
"Stephen Satchell" <list@fluent2.pyramid.net>
Cc: <linux-kernel@vger.kernel.org>, <linux-net@vger.kernel.org>,
<kernelnewbies@nl.linux.org>
Subject: Re: Job Announcements (was Linux TCP/IP Stack Developer)
Date: Sat, 11 Oct 2003 15:12:15 -0700 [thread overview]
Message-ID: <028b01c39044$bb2c89e0$2eedfea9@kittycat> (raw)
In-Reply-To: 20031011133541.0498ffa6.davem@redhat.com
From: "David S. Miller" <davem@redhat.com>
> On Sat, 11 Oct 2003 13:25:08 -0700
> Stephen Satchell <list@fluent2.pyramid.net> wrote:
>
> > At 10:58 AM 10/11/2003 -0700, you wrote:
> >
> > >By spamming job opennings to our kernel development lists where such
> > >things are not considered allowed, you fucknuts are basically
> > >guarenteeing that no kernel programmer with a brain is going to
> > >respect your company enough to apply for these jobs.
> > >
> > >Please stop posting this crap now.
> >
> > Are you speaking for yourself, or for Red Hat as well?
>
> I'm speaking as the vger.kernel.org list maintainer.
>
> Posting job offerings here has always been and will always be verboten
> here on these lists. And in particular technical people who join this
> list get a very bad taste in their mouth when someone advertises here
> be it for jobs or products.
>
> If there is no good place to look for Linux kernel development jobs,
> that isn't my problem. What is my problem is to enforce the rules
> of these lists at vger.kernel.org.
What you say and what Stephen says are both significant truths. I
wonder if Steve asked the wrong question. Might it be possible to
generate a specific "kernel jobs list" on vger and police it for
extrania as thoroughly as this list gets policed? Given the job
climate of late that might be a nice service to the community.
{^_^} Joanne
next prev parent reply other threads:[~2003-10-11 22:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-10 22:55 Linux TCP/IP Stack Developer hotjobs
2003-10-11 17:58 ` David S. Miller
2003-10-11 20:25 ` Job Announcements (was Linux TCP/IP Stack Developer) Stephen Satchell
2003-10-11 20:35 ` David S. Miller
2003-10-11 22:12 ` jdow [this message]
2003-10-11 22:11 ` David S. Miller
2003-10-11 21:29 ` Willy TARREAU
2003-10-11 22:16 ` Stephen Satchell
2003-10-11 23:39 ` Mark Mielke
2003-10-12 11:03 ` Jamie Lokier
2003-10-12 14:59 ` Stephen Satchell
2003-10-13 1:47 ` Adam Sulmicki
2003-10-13 1:58 ` Adam Sulmicki
2003-10-14 9:23 ` Jamie Lokier
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='028b01c39044$bb2c89e0$2eedfea9@kittycat' \
--to=jdow@earthlink.net \
--cc=davem@redhat.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=list@fluent2.pyramid.net \
/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