git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Camille Moncelier <moncelier@devlife.org>
Cc: Christian Couder <christian.couder@gmail.com>,
	Elijah Newren <newren@gmail.com>,
	Nick <oinksocket@letterboxes.org>, git <git@vger.kernel.org>
Subject: Re: cherry-pick fail when a symbolic link has been changed into a file or directory
Date: Sun, 07 Nov 2010 11:19:44 +0100	[thread overview]
Message-ID: <m239rdv3jz.fsf@igel.home> (raw)
In-Reply-To: <20101107104209.3e497c5b@cortex> (Camille Moncelier's message of "Sun, 7 Nov 2010 10:42:09 +0100")

Camille Moncelier <moncelier@devlife.org> writes:

> BTW, Is there a way using git bisect to find the "last bad commit",
> or maybe the "first good one" ?

It works the same as "find first bad one", you just have to exchange
"good" and "bad" (they really mean "before" and "after").

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

      reply	other threads:[~2010-11-07 10:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-04 11:56 cherry-pick fail when a symbolic link has been changed into a file or directory Camille Moncelier
2010-11-04 13:55 ` Christian Couder
2010-11-04 13:58   ` Christian Couder
2010-11-04 14:16   ` Camille Moncelier
2010-11-04 17:03     ` Christian Couder
2010-11-04 17:15       ` Camille Moncelier
2010-11-05  8:33         ` Christian Couder
     [not found]         ` <AANLkTimDWM69qvY5wdyzFu=g6htg12-K542PRR4bdDYq@mail.gmail.com>
2010-11-05  8:34           ` Christian Couder
2010-11-07  9:42             ` Camille Moncelier
2010-11-07 10:19               ` Andreas Schwab [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=m239rdv3jz.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=moncelier@devlife.org \
    --cc=newren@gmail.com \
    --cc=oinksocket@letterboxes.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 NNTP newsgroup(s).