public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Stan Shebs <shebs@shebs.cnchost.com>
To: Jason Molenda <jason-swarelist@molenda.com>
Cc: Bob Manson <manson@juniper.net>, overseers@sourceware.cygnus.com
Subject: Re: cygwin-xfree
Date: Sun, 21 May 2000 22:19:00 -0000	[thread overview]
Message-ID: <3928C520.87A991BA@shebs.cnchost.com> (raw)
Message-ID: <20000521221900.3AEapqrXBDda-qCdzVE_FvMBm5Lm3eweUxxSoOcMSpg@z> (raw)
In-Reply-To: <20000504131930.B19898@shell17.ba.best.com>

Jason Molenda wrote:
> 
> On Wed, May 03, 2000 at 09:12:14PM -0700, Bob Manson wrote:
> 
> > He was no kindly king.  He was the Ruler of Evil!  Evil, I tell you!
> > I quaked in fear whenver he typed!
> 
> It's true, it's all true.  Cygnus is actually a training ground
> for Evil,

Not true!  Don't you remember when we got the fan mail sent into
info@cygnus, telling us how great GNU was and how we Cygnites were
doing God's work?  Alas, it wasn't one of the paying customers...

> We
> should have (or present tense, should) convinced management to pony
> up for a full time person and hooked it into the rest of the
> company's organization.

For those who need to work on this, allow me to recommend the power
of the nag.  These days, managers are so interrupt-driven that the
one-time mail message gets lost in the noise.  Nagging serves the
dual purposes of regular reminder and effective increase in priority;
keeping the issue "paged in", as it were.  Once a week is good, daily
is usually too much, monthly is too sparse.  Be sure the nag includes
specific activities with dollars and dates, otherwise it degenerates
into whining, which is useless.

Stan

  parent reply	other threads:[~2000-05-21 22:19 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-30  6:08 cygwin-xfree Chris Faylor
2000-05-03 19:18 ` cygwin-xfree Chris Faylor
2000-12-30  6:08 ` cygwin-xfree Jeffrey A Law
2000-05-04  9:07   ` cygwin-xfree Jeffrey A Law
2000-12-30  6:08 ` cygwin-xfree Andrew Cagney
2000-05-03 19:30   ` cygwin-xfree Andrew Cagney
2000-12-30  6:08   ` cygwin-xfree Jim Kingdon
2000-05-03 19:47     ` cygwin-xfree Jim Kingdon
2000-12-30  6:08   ` cygwin-xfree Chris Faylor
2000-05-03 19:34     ` cygwin-xfree Chris Faylor
2000-12-30  6:08 ` cygwin-xfree Tom Tromey
2000-05-03 19:59   ` cygwin-xfree Tom Tromey
2000-12-30  6:08   ` cygwin-xfree Chris Faylor
2000-05-03 20:07     ` cygwin-xfree Chris Faylor
2000-12-30  6:08     ` cygwin-xfree Per Bothner
2000-05-03 23:21       ` cygwin-xfree Per Bothner
2000-12-30  6:08       ` cygwin-xfree Jim Kingdon
2000-05-04  4:35         ` cygwin-xfree Jim Kingdon
2000-12-30  6:08     ` cygwin-xfree Tom Tromey
2000-05-03 20:09       ` cygwin-xfree Tom Tromey
2000-12-30  6:08       ` libstdc++-v3 things that still are not working correctly Benjamin Kosnik
2000-05-03 20:14         ` Benjamin Kosnik
2000-12-30  6:08         ` Jeffrey A Law
2000-05-03 22:33           ` Jeffrey A Law
2000-12-30  6:08       ` cygwin-xfree Chris Faylor
2000-05-03 20:22         ` cygwin-xfree Chris Faylor
2000-12-30  6:08         ` cygwin-xfree Bob Manson
2000-05-03 21:11           ` cygwin-xfree Bob Manson
2000-12-30  6:08           ` cygwin-xfree Jason Molenda
2000-05-04 13:19             ` cygwin-xfree Jason Molenda
2000-12-30  6:08             ` cygwin-xfree Jim Kingdon
2000-05-07  6:32               ` cygwin-xfree Jim Kingdon
2000-12-30  6:08             ` Stan Shebs [this message]
2000-05-21 22:19               ` cygwin-xfree Stan Shebs
2000-12-30  6:08               ` cygwin-xfree Mark Galassi
2000-05-22  6:15                 ` cygwin-xfree Mark Galassi
2000-12-30  6:08         ` cygwin-xfree Jim Kingdon
2000-05-04  4:52           ` cygwin-xfree Jim Kingdon
2000-12-30  6:08           ` cygwin-xfree Chris Faylor
2000-05-04  7:48             ` cygwin-xfree Chris Faylor
2000-12-30  6:08 ` cygwin-xfree Jason Molenda
2000-05-03 19:45   ` cygwin-xfree Jason Molenda
2000-12-30  6:08   ` htdig, was cygwin-xfree Frank Ch. Eigler
2000-05-03 20:23     ` Frank Ch. Eigler
2000-12-30  6:08     ` Hans-Peter Nilsson
2000-05-06  2:43       ` Hans-Peter Nilsson
2000-12-30  6:08   ` cygwin-xfree Chris Faylor
2000-05-03 19:53     ` cygwin-xfree Chris Faylor

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=3928C520.87A991BA@shebs.cnchost.com \
    --to=shebs@shebs.cnchost.com \
    --cc=jason-swarelist@molenda.com \
    --cc=manson@juniper.net \
    --cc=overseers@sourceware.cygnus.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 read-only IMAP folder(s) and NNTP newsgroup(s).