From: Grant Edwards <grante@visi.com>
To: Keith Seitz <keiths@cygnus.com>
Cc: Fernando Nasser <fnasser@cygnus.com>, insight@sourceware.cygnus.com
Subject: Re: Patches for source path and SIGINT warning
Date: Mon, 13 Aug 2001 10:30:00 -0000 [thread overview]
Message-ID: <20010813123249.A7282@visi.com> (raw)
In-Reply-To: <Pine.GSO.4.33.0108131027380.22492-100000@makita.cygnus.com>
On Mon, Aug 13, 2001 at 10:28:21AM -0700, Keith Seitz wrote:
> On Mon, 13 Aug 2001, Grant Edwards wrote:
>
> > Did this problem get fixed?
>
> I believe it was.
>
> > I'm about to bundle up a weekly snapshot for use by my
> > customers, [...]
>
> Can I have some customers? :-)
You don't want them -- they cause all sorts of problems with
their entirely unreasonable demands that bugs be fixed and
suchlike.
--
Grant Edwards
grante@visi.com
prev parent reply other threads:[~2001-08-13 10:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20000825114434.C9351@visi.com>
[not found] ` <39BE9A66.5924143@cygnus.com>
2000-10-11 3:45 ` Patches for RDI stop code and general features Tim Chick
2000-10-11 10:06 ` Fernando Nasser
2001-08-13 8:45 ` Patches for source path and SIGINT warning Grant Edwards
2001-08-13 10:28 ` Keith Seitz
2001-08-13 10:30 ` Grant Edwards [this message]
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=20010813123249.A7282@visi.com \
--to=grante@visi.com \
--cc=fnasser@cygnus.com \
--cc=insight@sourceware.cygnus.com \
--cc=keiths@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).