unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Noah Lavine <noah.b.lavine@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: "Michael Lucy" <MichaelGLucy@gmail.com>,
	"Ludovic Courtès" <ludo@gnu.org>,
	guile-devel@gnu.org
Subject: Re: PEG Parser
Date: Sun, 6 Feb 2011 10:31:31 -0500	[thread overview]
Message-ID: <AANLkTin_p9gzEy_mdnkVFS792OJu4E1XoTqr2ofNgthj@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=L4KET0Z5CBDv_5_j811md+kUx9tcJt2gRPVfp@mail.gmail.com>

Hi,

> However, I have a suspicion something odd is going on and this does
> not contain all of the work it should from guile's repo. I ended up
> having to use git cherry-pick instead of git rebase because I had made
> a mistake when I first made my local peg branch. I checked out
> origin/wip-mlucy and then cherry-picked my commits on top of that.
>
> It worked well, but in one of my earlier attempts before I decided
> that git-rebase wasn't going to work, I saw that someone had renamed
> peg-sexp-compile to cg-match-func and added some more test cases to
> peg.test. Now I don't see those additions, and if they're not in
> wip-mlucy then I'm not sure where to find them. Does anyone know where
> I should look for that?

Never mind that, sorry. There was a rename, but I was on the correct
side of it. I somehow looked at old code and got confused and thought
it was new code. The patches should apply cleanly to the head of
wip-mlucy, and everything should be fine.

Noah



  reply	other threads:[~2011-02-06 15:31 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-13 21:29 PEG Parser Noah Lavine
2011-01-17 21:32 ` Ludovic Courtès
2011-01-21 15:23   ` Noah Lavine
2011-01-22 21:02     ` Ludovic Courtès
2011-01-24  1:29       ` Noah Lavine
2011-01-24 20:55         ` Ludovic Courtès
2011-01-27  1:40         ` Noah Lavine
2011-01-27  2:23           ` Michael Lucy
2011-01-27  2:38             ` Noah Lavine
2011-01-27  3:02               ` Michael Lucy
2011-01-27  5:17                 ` Noah Lavine
2011-01-28  3:25                   ` Noah Lavine
2011-01-28  5:13                     ` Michael Lucy
2011-01-28 15:48                   ` Andy Wingo
2011-01-29  3:07                     ` Noah Lavine
2011-01-29  4:15                       ` Michael Lucy
2011-01-29 11:34                         ` Andy Wingo
2011-01-29 19:37                           ` Noah Lavine
2011-01-30 11:43                             ` Andy Wingo
2011-02-02  0:26                               ` Noah Lavine
2011-02-06 15:31                                 ` Noah Lavine [this message]
2011-02-18 22:03                                 ` Andy Wingo
2011-02-23 15:10                                   ` Noah Lavine
2011-03-04 10:52                                     ` Andy Wingo
2011-03-04 13:09                                       ` Noah Lavine
2011-01-29 11:33                       ` Andy Wingo
  -- strict thread matches above, loose matches on Subject: below --
2010-05-27  5:19 Michael Lucy

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=AANLkTin_p9gzEy_mdnkVFS792OJu4E1XoTqr2ofNgthj@mail.gmail.com \
    --to=noah.b.lavine@gmail.com \
    --cc=MichaelGLucy@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@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).