From: Noah Lavine <noah.b.lavine@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Names for PEG Functions
Date: Thu, 19 Jan 2012 22:18:20 -0500 [thread overview]
Message-ID: <CA+U71=PX4kMCpoEbjreRaptGirWRMQsdfWvZj+j_X==Zmb7WDQ@mail.gmail.com> (raw)
In-Reply-To: <CA+U71=NWvSE5qL_u3wq1xcfc4EGfBjLjmwWm_YHvvmPhWQ2g1A@mail.gmail.com>
I've run into trouble because of my problems building master. I'll
have to work around that, so it won't happen tonight.
On Thu, Jan 19, 2012 at 8:54 AM, Noah Lavine <noah.b.lavine@gmail.com> wrote:
> Sorry for the delay.
>
> I haven't thought about the PEG stuff in a long time, but looking
> back, I'm pretty sure I didn't change the names yet. I will try to do
> it tonight (in GMT-5). I agree, it would be great to have the PEG
> stuff finished.
>
> On Thu, Jan 19, 2012 at 4:53 AM, Andy Wingo <wingo@pobox.com> wrote:
>> On Wed 04 Jan 2012 19:12, Andy Wingo <wingo@pobox.com> writes:
>>
>>> On Mon 03 Oct 2011 20:21, Noah Lavine <noah.b.lavine@gmail.com> writes:
>>>
>>>> I hate to make more work for people, but I think the PEG module is
>>>> almost ready for merging, and could probably be merged if we resolved
>>>> this names issue. Any other thoughts?
>>>
>>> Have you updated the wip-peg branch? I don't remember who is waiting
>>> for whom any more, but reviewing the threads, it seems that we generally
>>> agreed on some name changes here.
>>
>> A kind ping here :) It would be lovely to get the peg stuff in for
>> 2.0.5.
>>
>> Andy
>> --
>> http://wingolog.org/
next prev parent reply other threads:[~2012-01-20 3:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 20:13 Names for PEG Functions Noah Lavine
2011-09-21 20:45 ` Andy Wingo
2011-09-22 17:56 ` Noah Lavine
2011-10-04 0:21 ` Noah Lavine
2012-01-04 18:12 ` Andy Wingo
2012-01-19 9:53 ` Andy Wingo
2012-01-19 13:54 ` Noah Lavine
2012-01-20 3:18 ` Noah Lavine [this message]
2012-01-22 20:15 ` Noah Lavine
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='CA+U71=PX4kMCpoEbjreRaptGirWRMQsdfWvZj+j_X==Zmb7WDQ@mail.gmail.com' \
--to=noah.b.lavine@gmail.com \
--cc=guile-devel@gnu.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).