From: Dan Nicolaescu <dann@ics.uci.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Problem report #86
Date: Tue, 04 Jul 2006 23:14:12 -0700 [thread overview]
Message-ID: <200607050614.k656ECV9016839@oogie-boogie.ics.uci.edu> (raw)
In-Reply-To: <m3lkrabz74.fsf@kfs-l.imdomain.dk> (Kim F. Storm's message of "Mon, 03 Jul 2006 15:22:23 +0200")
storm@cua.dk (Kim F. Storm) writes:
> Dan Nicolaescu <dann@ics.uci.edu> writes:
>
> > This appeared around June 12th.
> > The warning seems correct to me. Does anybody know what is the right
> > way to fix this?
>
> I installed a fix.
Thanks!
This was the last problem report that was unresolved.
prev parent reply other threads:[~2006-07-05 6:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-02 4:13 Problem report #86 Dan Nicolaescu
2006-07-03 13:22 ` Kim F. Storm
2006-07-05 6:14 ` Dan Nicolaescu [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=200607050614.k656ECV9016839@oogie-boogie.ics.uci.edu \
--to=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).