public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Brown <mtd@davidb.org>
To: Bill Gatliff <bgat@billgatliff.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Node CRC failures in latest mainline git?
Date: Wed, 30 Jul 2008 21:56:24 -0700	[thread overview]
Message-ID: <20080731045624.GA24431@old.davidb.org> (raw)
In-Reply-To: <48913EA3.9080603@billgatliff.com>

On Wed, Jul 30, 2008 at 11:25:07PM -0500, Bill Gatliff wrote:

>Were I more competent with git, I would figure out how to bisect down to the
>patch that caused the problem.  That's still a bit out of my skillset at the
>moment, unfortunately--- I've done bisects successfully in the past, but for
>some reason I just can't get git to play along this time...

I just recently asked a question on the git mailing list, and Linus replied
with these instructions for bisecting through a merge.  Basically, you
create a temporary branch where you flatten the merge, using rebase, and
then bisect that.

   # create a test-branch with the 'remote' side of the merge
   git checkout -b test-branch merge^2

   # rebase that remote side on top of the local side
   git rebase merge^

Haven't actually needed to try it, but let me know if it doesn't work, and
I'll figure out the proper incantation.

David Brown

  parent reply	other threads:[~2008-07-31  4:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-31  4:25 Node CRC failures in latest mainline git? Bill Gatliff
2008-07-31  4:44 ` Bill Gatliff
2008-08-01 20:59   ` David Woodhouse
2008-08-01 21:01     ` Bill Gatliff
2008-08-01 21:14       ` David Woodhouse
2008-07-31  4:56 ` David Brown [this message]
2008-07-31 20:28   ` Bill Gatliff
2008-08-01  2:47     ` David Brown
2008-08-01  3:48       ` Bill Gatliff

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=20080731045624.GA24431@old.davidb.org \
    --to=mtd@davidb.org \
    --cc=bgat@billgatliff.com \
    --cc=linux-mtd@lists.infradead.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