From: Andy Wingo <wingo@pobox.com>
To: guile-devel <guile-devel@gnu.org>
Subject: bugfix regarding recent master->vm merge rewrites history
Date: Tue, 17 Mar 2009 20:57:24 +0100 [thread overview]
Message-ID: <m31vsvsz17.fsf@pobox.com> (raw)
Hi,
There was a problem in the conversion of subrs to double-cells, in which
the additional cells were not being marked. This was quite a number of
commits ago, on master, and having such a large period in which that bug
was present is not good for bisection. So I've revived the VM branch.
It's the same as master, except commit
325226dad9ab6f0488500e7381a5d1c07dc9ae91 was retroactively introduced in
the history.
Anyway, all this to say that VM has been rewritten, and I'd like to copy
it over to master. This is fine, but whenever you pull and get a "forced
update" you always wonder why that was -- and this is why. If no one
objects, I'll forcibly reset master to vm later this evening.
Sorry for the confusion. Play around in gitk if it's not clear to you:
gitk origin/master...origin/vm
All of the merges are from when I was trying to figure out which patch
introduced the bug.
Cheers,
Andy
--
http://wingolog.org/
next reply other threads:[~2009-03-17 19:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 19:57 Andy Wingo [this message]
2009-03-17 20:56 ` bugfix regarding recent master->vm merge rewrites history 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=m31vsvsz17.fsf@pobox.com \
--to=wingo@pobox.com \
--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).