unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: David Fang <fang@csl.cornell.edu>
Cc: bug-guile@gnu.org
Subject: Re: guile 1.9.14 crash on *-darwin*
Date: Thu, 10 Feb 2011 10:23:34 +0100	[thread overview]
Message-ID: <m3tygcckfd.fsf@unquote.localdomain> (raw)
In-Reply-To: <20110127141616.B65525@fiji.csl.cornell.edu> (David Fang's message of "Thu, 27 Jan 2011 14:17:14 -0500 (EST)")

On Thu 27 Jan 2011 20:17, David Fang <fang@csl.cornell.edu> writes:

> 	Thus attached, bzip2-html.  (is about 115k uncompressed)
> Thanks for investigating.

Hi,

Please try again with git.  It should give a different error; I don't
think your error is entirely fixed.

However this time, please send the logs to the list, bzipped or not as
appropriate, not a web page.  Thanks :)

Andy
-- 
http://wingolog.org/



      reply	other threads:[~2011-02-10  9:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-25 21:49 guile 1.9.14 crash on *-darwin* David Fang
2011-01-27 10:26 ` Andy Wingo
2011-01-27 19:17   ` David Fang
2011-02-10  9:23     ` 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=m3tygcckfd.fsf@unquote.localdomain \
    --to=wingo@pobox.com \
    --cc=bug-guile@gnu.org \
    --cc=fang@csl.cornell.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).