From: lucio@proxima.alt.za
To: 9fans@cse.psu.edu
Subject: Re: [9fans] suicide of the new /bin/gs
Date: Fri, 9 Mar 2007 19:23:00 +0200 [thread overview]
Message-ID: <ebacc44eeb0b5dd286af9256bf124b3b@proxima.alt.za> (raw)
In-Reply-To: <a414c1c26c46558eb543dbf6b4a62b5a@voidness.de>
> However, I'm not very sure about these guesses and I don't know how to
> fix this. :/
Hm, I submitted that patch after Andrey suggested it and I thought it
had worked successfully for what it was intended (see previous mail
about APE failures). Perhaps it ought to have been tested more
carefully and perhaps it was more pervasive than I thought. It may be
advisable to revert it.
++L
next prev parent reply other threads:[~2007-03-09 17:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 16:50 Heiko Dudzus
2007-03-09 2:58 ` Joel C. Salomon
2007-03-09 11:22 ` Heiko Dudzus
2007-03-09 17:23 ` lucio [this message]
2007-03-14 13:52 Heiko Dudzus
2007-03-14 13:57 ` erik quanstrom
2007-03-14 14:49 Heiko Dudzus
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ebacc44eeb0b5dd286af9256bf124b3b@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@cse.psu.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 NNTP newsgroup(s).