From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] more lucent bad news - another 15,000 to 20,000 jobs to go
Date: Wed, 25 Jul 2001 08:19:38 -0400 [thread overview]
Message-ID: <20010725121940.A9E82199F6@mail.cse.psu.edu> (raw)
On Wed Jul 25 04:11:25 EDT 2001, matt@proweb.co.uk wrote:
>
> Lucent to cut another 15,000 to 20,000 jobs
>
> http://www.theregister.co.uk/content/7/20608.html
Is it a positive note that Lucent is no longer 'the struggling
telecommunications manufacturer' but is now 'the embattled telecommunications
manufacturer'?
next reply other threads:[~2001-07-25 12:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-25 12:19 jmk [this message]
2001-07-26 1:01 ` greg andruk
2001-07-26 1:16 ` Jerry Pearson
-- strict thread matches above, loose matches on Subject: below --
2001-07-26 3:08 David Gordon Hogan
2001-07-26 4:15 ` Jerry Pearson
2001-07-25 1:40 [9fans] commercial deployment Rick Hohensee
2001-07-25 3:52 ` Boyd Roberts
2001-07-25 8:10 ` [9fans] more lucent bad news - another 15,000 to 20,000 jobs to go Matt
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=20010725121940.A9E82199F6@mail.cse.psu.edu \
--to=jmk@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).