From: Ken Raeburn <raeburn@cygnus.com>
To: Bryan Ford <baford@schirf.cs.utah.edu>
Cc: gas2@cygnus.com
Subject: Re: 16-bit i386 code support in GAS
Date: Wed, 09 Nov 1994 23:35:00 -0000 [thread overview]
Message-ID: <9411100735.AA24627@cujo.cygnus.com> (raw)
In-Reply-To: <199411091906.MAA25430@schirf.cs.utah.edu>
Date: Wed, 09 Nov 94 12:06:51 MST
From: Bryan Ford <baford@schirf.cs.utah.edu>
I've sent messages (including bug _fixes_, not just reports)
to bug-gnu-utils several times before, and have never gotten any
kind of response whatsoever - my mail just disappears into the void. :-)
Yeah, I've been known to not respond very quickly, or sometimes at
all, depending on (among other things) the severity of the problem,
whether it's been reported before, whether I've responded to another
posting of the same bug on bug-gnu-utils already, whether I've got a
fix, how hard it looks to fix, how informative the bug report is, how
swamped I feel with work I'm doing for Cygnus customers, what I had
for breakfast, ... I'm not especially organized or disciplined when
it comes to dealing with mail.
But I'll usually keep the message around unless I've got some reason
for thinking I won't need it -- for example, it describes a problem I
think is already fixed, or something -- and I don't see your message
among my saved mail. How long ago was it? Is the problem fixed in
binutils-2.5.2? If it isn't, please resend it to me personally.
next prev parent reply other threads:[~1994-11-09 23:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199411091455.HAA25021@schirf.cs.utah.edu>
1994-11-09 7:20 ` H.J. Lu
1994-11-09 10:49 ` Ken Raeburn
1994-11-09 11:06 ` Bryan Ford
1994-11-09 23:35 ` Ken Raeburn [this message]
1994-11-10 6:57 ` Bryan Ford
1994-11-10 11:51 ` Ken Raeburn
1994-11-09 19:22 ` Rick Sladkey
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=9411100735.AA24627@cujo.cygnus.com \
--to=raeburn@cygnus.com \
--cc=baford@schirf.cs.utah.edu \
--cc=gas2@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).