linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Geoff Thorpe <Geoff.Thorpe@freescale.com>
To: Olof Johansson <olof@lixom.net>
Cc: linuxppc-dev@ozlabs.org, linuxppc-embedded@ozlabs.org,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [JOB] Senior Embedded Linux Video Engineer
Date: Fri, 14 Jul 2006 14:40:08 -0400	[thread overview]
Message-ID: <44B7E508.7020700@freescale.com> (raw)
In-Reply-To: <20060714180309.GA9121@pb15.lixom.net>

Olof Johansson wrote:

>Personally, I don't mind getting the ads just to know who is growing
>out there and so on, but I don't want them sorted into the folder with
>technical stuff, and I don't want to rely on people tagging the subject
>right.
>  
>

In this case, a list moderator was contacted prior to the post. So... 
why not just extend the idea and have potential employers[1] provide 
their "openings" (erm) to such a moderator who sends a not-too-frequent 
digest to the list encapsulating any/all such offerings. That way, the 
subject *will* be tagged correctly, the rate of "off-topic" postings is 
inherently throttled/coalesced, and anyone who might be remotely 
interested will be exposed to such opportunities without having to 
actively go searching (ipso facto, those HR types will be less inclined 
to carpet-bomb the entire internet for fear that their offerings go 
otherwise unnoticed). Hell, if the subject header was appropriately 
keyworded - Wolfgang could even procmail it to /dev/null ;-)

[1] this could also cover other commercial/potential-list-abuse subjects 
like speaking engagements, survey requests, [tbd]. If it got too big, it 
could be replaced with a summary of headings and URLs. Whatever.

Just my first-glance $0.02,
Geoff

  reply	other threads:[~2006-07-14 18:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-13 20:33 [JOB] Senior Embedded Linux Video Engineer Davenport, Richard
2006-07-14  8:07 ` Christoph Hellwig
2006-07-14  8:43   ` Stephen Rothwell
2006-07-14 11:22     ` Wolfgang Denk
2006-07-14 14:35       ` bbosch
2006-07-14 14:58         ` John W. Linville
2006-07-14 15:20           ` jschopp
2006-07-14 16:21         ` Wolfgang Denk
2006-07-14 16:38           ` Linas Vepstas
2006-07-14 18:41             ` Frank
2006-07-14 19:14         ` Segher Boessenkool
2006-07-14 17:29       ` Tim Bird
2006-07-14 18:03         ` Olof Johansson
2006-07-14 18:40           ` Geoff Thorpe [this message]
2006-07-16 15:12             ` Wolfgang Denk
2006-07-17  1:12               ` David H. Lynch Jr.
2006-07-17  3:28               ` Geoff Thorpe
2006-07-14 19:13           ` Tim Bird
2006-07-14 19:17             ` Olof Johansson
2006-07-15  3:23             ` David H. Lynch Jr.
  -- strict thread matches above, loose matches on Subject: below --
2006-07-13 20:51 Davenport, Richard

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=44B7E508.7020700@freescale.com \
    --to=geoff.thorpe@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=olof@lixom.net \
    --cc=sfr@canb.auug.org.au \
    /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).