From: Adam Schreiber <INVALID.NOREPLY@gnu.org>
To: Neil Jerram <neil@ossau.uklinux.net>,
Martin Pitt <martin@piware.de>,
Adam Schreiber <sadam@clemson.edu>,
bug-guile@gnu.org
Subject: [bug #24009] does not check for short write()s
Date: Wed, 29 Oct 2008 16:58:00 +0000 [thread overview]
Message-ID: <20081029-165800.sv70543.23608@savannah.gnu.org> (raw)
In-Reply-To: <20080806-200830.sv185.7659@savannah.gnu.org>
Follow-up Comment #2, bug #24009 (project guile):
This bug breaks building GNOME 2.26 in jhbuild because it treats warnings
like errors.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?24009>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
next prev parent reply other threads:[~2008-10-29 16:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 11:51 [bug #24009] does not check for short write()s Martin Pitt
2008-08-06 20:08 ` Neil Jerram
2008-10-29 16:58 ` Adam Schreiber [this message]
2008-10-30 22:44 ` anonymous
2008-10-31 2:45 ` Adam Schreiber
2008-11-30 18:10 ` Ludovic Courtès
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081029-165800.sv70543.23608@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=bug-guile@gnu.org \
--cc=martin@piware.de \
--cc=neil@ossau.uklinux.net \
--cc=sadam@clemson.edu \
/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).