From: Andy Wingo <INVALID.NOREPLY@gnu.org>
To: Cedric Cellier <rixed@free.fr>, Andy Wingo <wingo@pobox.com>,
bug-guile@gnu.org
Subject: [bug #31941] [1-9-14] FAIL: test-scm-with-guile on MIPS
Date: Sat, 22 Jan 2011 18:55:39 +0000 [thread overview]
Message-ID: <20110122-185538.sv20118.27869@savannah.gnu.org> (raw)
In-Reply-To: <20101222-092630.sv11689.12248@savannah.gnu.org>
Update of bug #31941 (project guile):
Status: None => Fixed
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #3:
I believe I have fixed this in Git. Please reopen if this is still an issue
for you.
Thanks for the report,
Andy
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?31941>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
prev parent reply other threads:[~2011-01-22 18:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 6:23 [bug #31941] [1-9-14] FAIL: test-scm-with-guile on MIPS Cedric Cellier
2010-12-21 7:43 ` Cedric Cellier
2010-12-22 8:26 ` Cedric Cellier
2011-01-22 18:55 ` Andy Wingo [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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110122-185538.sv20118.27869@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=bug-guile@gnu.org \
--cc=rixed@free.fr \
--cc=wingo@pobox.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).