From: Eli Zaretskii <eliz@is.elta.co.il>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: building 21.2 on sparc-sun-solaris2.7, conflicting types for memmove
Date: Thu, 1 Aug 2002 08:30:00 +0300 (IDT) [thread overview]
Message-ID: <Pine.SUN.3.91.1020801082856.20714D-100000@is> (raw)
In-Reply-To: <200207311747.g6VHldU1009456@cascade.cs.ubc.ca>
On Wed, 31 Jul 2002, Matthew Wilkins wrote:
> sorry that i bothered you with a known problem
No need to be sorry: you saw a bug and reported it, which is what an
Emacs user is supposed to do. If this wasn't reported earlier, your
report would have caused us to fix the bug.
Thanks!
next prev parent reply other threads:[~2002-08-01 5:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-31 17:47 building 21.2 on sparc-sun-solaris2.7, conflicting types for memmove Matthew Wilkins
2002-08-01 5:30 ` Eli Zaretskii [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-30 20:22 Matthew Wilkins
2002-07-31 10:46 ` Eli Zaretskii
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=Pine.SUN.3.91.1020801082856.20714D-100000@is \
--to=eliz@is.elta.co.il \
--cc=bug-gnu-emacs@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).