From: Andy Wingo <wingo@pobox.com>
To: Hans Aberg <haberg-1@telia.com>
Cc: 10012@debbugs.gnu.org
Subject: bug#10012: Guile-1.9.15: broken pipe
Date: Wed, 16 Nov 2011 22:43:01 +0100 [thread overview]
Message-ID: <87zkfvkal6.fsf@pobox.com> (raw)
In-Reply-To: <78BE89D2-FB57-43F7-8954-418E223DEE71@telia.com> (Hans Aberg's message of "Wed, 16 Nov 2011 21:15:15 +0100")
On Wed 16 Nov 2011 21:15, Hans Aberg <haberg-1@telia.com> writes:
> BTW, your new system with a plethora of mail addresses makes it very had
> to sort it automatically. I gather, the idea is to follow in on the web
> somewhere.
Actually, the idea is to follow over mail. See
http://debbugs.gnu.org/Advanced.html for more details on the tracker.
I haven't updated my filters yet either, but I will at some point.
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2011-11-16 21:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 17:38 bug#10012: Guile-1.9.15: broken pipe Hans Aberg
2011-11-16 19:29 ` Andy Wingo
[not found] ` <78BE89D2-FB57-43F7-8954-418E223DEE71@telia.com>
2011-11-16 21:43 ` 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=87zkfvkal6.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=10012@debbugs.gnu.org \
--cc=haberg-1@telia.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).