unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Daniel Kraft <d@domob.eu>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: upcoming patches
Date: Mon, 19 Oct 2009 20:26:06 +0200	[thread overview]
Message-ID: <m3ljj7s0jl.fsf@pobox.com> (raw)
In-Reply-To: <4ADC5CED.8070804@domob.eu> (Daniel Kraft's message of "Mon, 19 Oct 2009 14:34:53 +0200")

On Mon 19 Oct 2009 14:34, Daniel Kraft <d@domob.eu> writes:

> Hi Andy,
>
> Andy Wingo wrote:
>>   3) Merge Daniel's work
>>
>>      This will involve some updating for the case-lambda tree-il
>>      changes, but the ecmascript and brainfuck changes have not been
>>      difficult to make.
>
> I've not yet done so but plan to keep on working there with some stuff
> (as I already mentioned, like defalias) as soon as I find some time. Two
> questions:
>
> * Do we want to freeze my branch for your work there, so I'll hold
> this off?

I would say, keep on trucking :) And keep the list informed of what
you're up to, please. If I'm able to merge something e.g. this weekend,
we'll just rebase any extra patches you have.

> * Does the case-lambda stuff mean that the branch won't currently work
> when I pull from master?  So, I should not do this until you did the
> update?  Or can I when restarting work to be up-to-date?

It won't work once wip-case-lambda gets merged. Some slight changes will
be necessary.

Andy
-- 
http://wingolog.org/




  reply	other threads:[~2009-10-19 18:26 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
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 [this message]
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=m3ljj7s0jl.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=d@domob.eu \
    --cc=guile-devel@gnu.org \
    /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).