From: Andy Wingo <wingo@pobox.com>
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-devel@gnu.org
Subject: Re: vm status update
Date: Tue, 10 Mar 2009 22:04:56 +0100 [thread overview]
Message-ID: <m3wsaxw0lj.fsf@pobox.com> (raw)
In-Reply-To: <87d4creiyv.fsf@arudy.ossau.uklinux.net> (Neil Jerram's message of "Sun, 08 Mar 2009 22:40:56 +0000")
On Sun 08 Mar 2009 23:40, Neil Jerram <neil@ossau.uklinux.net> writes:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>>> Anyway, that's where I am. Bug-wise we still have a bug in backtraces,
>>> which I need to pin down at some point, and update docs -- but generally
>>> speaking we're mergeable. What do people think, should I be working on
>>> master at some point?
>>
>> Sure. Neil: what do you think?
>
> No problem, I'm happy for Andy to merge now.
Great, I'll get to this within a week or so.
>> Looking at `vm', it's been sometime
>> since the last merge with `master', so it'd be worth checking that
>> things still work.
>
> I guess that would mean merging master into vm first, and checking
> that, then merging vm into master.
Yep.
Cheers,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2009-03-10 21:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 19:52 vm status update Andy Wingo
2009-03-06 22:31 ` Ludovic Courtès
2009-03-08 22:40 ` Neil Jerram
2009-03-10 21:04 ` Andy Wingo [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-14 22:32 Andy Wingo
2009-02-16 11:47 ` Marijn Schouten (hkBst)
2009-03-08 11:49 ` Neil Jerram
2009-03-10 21:36 ` Andy Wingo
2009-03-12 20:49 ` Neil Jerram
2009-01-11 17:35 Andy Wingo
2009-01-13 8:05 ` Ludovic Courtès
2008-12-26 17:24 Andy Wingo
2008-12-28 22:50 ` Neil Jerram
2009-01-05 16:06 ` Ludovic Courtès
2009-01-05 16:45 ` Neil Jerram
2009-01-05 19:53 ` Ludovic Courtès
2009-01-05 17:57 ` Andy Wingo
2009-01-05 21:03 ` Ludovic Courtès
2009-01-06 9:52 ` Andy Wingo
2009-01-06 14:54 ` Ludovic Courtès
2008-09-13 15:59 Andy Wingo
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=m3wsaxw0lj.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=neil@ossau.uklinux.net \
/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).