From: bdwalton@gmail.com (Ben Walton)
Subject: [sup-talk] Inconsistent inbox after restart
Date: Thu, 30 Apr 2009 09:10:20 -0400 [thread overview]
Message-ID: <f96e0240904300610n741d83aq95dd0c4b10876243@mail.gmail.com> (raw)
In-Reply-To: <1241095872-sup-9569@sgoldmanlinux.tower-research.com>
On Thu, Apr 30, 2009 at 8:51 AM, Steve Goldman
<sgoldman at tower-research.com> wrote:
> Excerpts from Tyberius Prime's message of Thu Apr 30 03:11:29 -0400 2009:
>> For me it seems to be messages that have been saved 'hours' ago by pressing $.
>
> I have confirmed that 0.7 is fine, but master is not. ?So we just have
> to track down which commit(s) in between broke it...
git-bisect to the rescue? Anyone experiencing this and comfortable
with git that wants to track down where the problem was introduced?
It may take a little while, unless the problem can be recreated at
will, but the bisect tool is awesome for situations like this.
-Ben
--
---------------------------------------------------------------------------------------------------------------------------
Ben Walton <bdwalton at gmail.com>
"With or without religion, good people can behave well and bad people
can do evil; but for good people to do evil?that takes religion. "
-Steven Weinberg
---------------------------------------------------------------------------------------------------------------------------
next prev parent reply other threads:[~2009-04-30 13:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 19:19 Steve Goldman
2009-04-29 8:17 ` Tyberius Prime
2009-04-29 8:40 ` Nicolas Pouillard
2009-04-29 8:37 ` Tyberius Prime
2009-04-29 18:10 ` William Morgan
2009-04-30 7:11 ` Tyberius Prime
2009-04-30 12:51 ` Steve Goldman
2009-04-30 13:10 ` Ben Walton [this message]
2009-04-30 13:36 ` William Morgan
2009-04-30 14:23 ` Steve Goldman
[not found] ` <f96e0240904300729l1493160eqdcc642af5aae1c15@mail.gmail.com>
2009-05-01 20:23 ` Steve Goldman
2009-05-04 13:32 ` William Morgan
2009-05-04 13:46 ` Steve Goldman
2009-04-30 13:19 ` William Morgan
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=f96e0240904300610n741d83aq95dd0c4b10876243@mail.gmail.com \
--to=bdwalton@gmail.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