From: bert hubert <ahu@ds9a.nl>
To: linux-kernel@vger.kernel.org
Subject: Linux Weekly News dying - any help?
Date: Fri, 26 Jul 2002 11:28:46 +0200 [thread overview]
Message-ID: <20020726092846.GA3542@outpost.ds9a.nl> (raw)
I read this last Thursday on lwn.net:
The end result is that next week's LWN Weekly Edition (August 1)
will be the last. This has not been an easy decision to make, to say
the least. But, barring some sort of last minute miracle (do contact
us if you have one, please!), we do not see any alternative
We bought some advertising on LWN but can of course not keep them alive
ourselves. Does anybody here have ideas on how to keep them in business?
See http://lwn.net
Regards,
bert hubert
--
http://www.PowerDNS.com Versatile DNS Software & Services
http://www.tk the dot in .tk
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
next reply other threads:[~2002-07-26 9:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-26 9:28 bert hubert [this message]
2002-07-26 10:07 ` Linux Weekly News dying - any help? jbradford
2002-07-26 10:22 ` Russell King
2002-07-26 10:35 ` bert hubert
2002-07-26 10:48 ` jbradford
2002-07-26 15:53 ` Rik van Riel
2002-07-27 23:51 ` Daniel Phillips
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=20020726092846.GA3542@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--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