From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Christian Couder <chriscool@tuxfamily.org>, git@vger.kernel.org
Subject: Re: help reverting a merge
Date: Mon, 30 Nov 2009 16:06:50 -0800 [thread overview]
Message-ID: <4B145E1A.9040304@gmail.com> (raw)
In-Reply-To: <20091130081315.GA587@coredump.intra.peff.net>
First things first is I owe you a great thanks
for teaching me how to do a rebase.. :-)
took a while, and still a bit confusing
but I managed to do exactly what you
had written down.
bad thing is somehow the bisect came up
with no results. probably will do another bisect,
just to make sure things are in the right
direction, and the try the rebase again.
Again Thanks for the help/info on this.
Justin P. Mattock
prev parent reply other threads:[~2009-12-01 0:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-29 23:24 help reverting a merge Justin Mattock
2009-11-30 8:13 ` Jeff King
2009-11-30 8:31 ` Justin P. Mattock
2009-12-01 0:06 ` Justin P. Mattock [this message]
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=4B145E1A.9040304@gmail.com \
--to=justinmattock@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=peff@peff.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 NNTP newsgroup(s).