From: Dave Jones <davej@redhat.com>
To: trinity@vger.kernel.org
Subject: breakage on master.
Date: Tue, 3 Jun 2014 16:54:11 -0400 [thread overview]
Message-ID: <20140603205411.GA32313@redhat.com> (raw)
I just committed some code changing how logging works so that the
post-mortem dumping has a possibility of actually working.
It looks a lot closer to how I want it to be, but it does seem to have
a number of bugs right now which may take a couple days to nail down.
unless you're feeling brave, either stick with the 1.4 release,
or 8127f706044297d92c7448a075be51dff73d747a which was the last
'known good' commit before last nights carnage.
I hope to be on top of things in a day or two.
Dave
next reply other threads:[~2014-06-03 20:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 20:54 Dave Jones [this message]
2014-06-06 17:54 ` breakage on master Dave Jones
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140603205411.GA32313@redhat.com \
--to=davej@redhat.com \
--cc=trinity@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.