From: Neil Jerram <neil@ossau.uklinux.net>
To: Andy Wingo <wingo@pobox.com>
Cc: "Mark H. Weaver" <mhw@netris.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: upcoming patches
Date: Mon, 19 Oct 2009 22:08:17 +0100 [thread overview]
Message-ID: <87tyxvks72.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <m3pr8js0m8.fsf@pobox.com> (Andy Wingo's message of "Mon, 19 Oct 2009 20:24:31 +0200")
Andy Wingo <wingo@pobox.com> writes:
> Oh no, I haven't seen a new one either. I was just going to take a look
> at the old one again and see how much work it needed -- because it's not
> fair to Daniel to keep his work in limbo, IMO.
True - but I thought Mark's patch was an orthogonal optimisation, and
hence that Daniel's work shouldn't depend on it. Is that wrong?
Neil
next prev parent reply other threads:[~2009-10-19 21:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-18 10:38 upcoming patches Andy Wingo
2009-10-18 21:43 ` Neil Jerram
2009-10-19 18:24 ` Andy Wingo
2009-10-19 21:08 ` Neil Jerram [this message]
2009-10-19 21:17 ` Andy Wingo
2009-10-20 16:47 ` Mark H Weaver
2009-10-20 19:19 ` Andy Wingo
2009-10-19 12:34 ` Daniel Kraft
2009-10-19 18:26 ` Andy Wingo
2009-10-27 20:15 ` Andy Wingo
2009-10-27 21:17 ` Neil Jerram
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=87tyxvks72.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.org \
--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).