From: "Davis Herring" <herring@lanl.gov>
To: "Dan Nicolaescu" <dann@ics.uci.edu>
Cc: emacs-devel@gnu.org
Subject: Re: problem report #99
Date: Mon, 1 Dec 2008 09:49:53 -0800 (PST) [thread overview]
Message-ID: <39558.128.165.123.18.1228153793.squirrel@webmail.lanl.gov> (raw)
In-Reply-To: <39538.128.165.123.18.1228153501.squirrel@webmail.lanl.gov>
My analysis for the "first #99" applies to all four of them, since they
analyze the same portion of code; perhaps that's why they got the same
number. Anyway: #2: no bug, #3: no bug, and #4: no bug.
Davis
--
This product is sold by volume, not by mass. If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during
shipping.
prev parent reply other threads:[~2008-12-01 17:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 15:57 problem report #99 Dan Nicolaescu
2008-12-01 17:45 ` Davis Herring
2008-12-01 17:49 ` Davis Herring [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=39558.128.165.123.18.1228153793.squirrel@webmail.lanl.gov \
--to=herring@lanl.gov \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).