All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent van Ravesteijn <vfr@lyx.org>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Why can't I use git-bisect to find the first *good* commit?
Date: Mon, 28 Mar 2011 14:39:12 +0200	[thread overview]
Message-ID: <4D908170.2020207@lyx.org> (raw)
In-Reply-To: <AANLkTinQ0rCw2ydisHra779r6_iSOxqRwOStpJrNbx7h@mail.gmail.com>


> Why can't bisect just do the right thing here and accept that your
> more recent revesion is the good one, and the old one is the bad one?

There was a recent discussion about this:

http://article.gmane.org/gmane.comp.version-control.git/165433

Vincent

  parent reply	other threads:[~2011-03-28 12:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-28  9:32 Why can't I use git-bisect to find the first *good* commit? Ævar Arnfjörð Bjarmason
2011-03-28 10:39 ` Andreas Ericsson
2011-03-28 12:22 ` code.sculptor
2011-03-28 12:58   ` Matthieu Moy
2011-03-28 12:39 ` Vincent van Ravesteijn [this message]
2011-03-28 14:04   ` Christian Couder
2011-03-28 14:29 ` Andrew Garber
2011-03-28 14:40   ` Johannes Sixt
2011-03-28 17:18     ` Andrew Garber
2011-03-28 17:33       ` Matthieu Moy
2011-03-28 17:45         ` Andrew Garber
2011-03-28 17:55           ` Matthieu Moy
2011-03-28 18:12             ` Andrew Garber
2011-03-28 18:23               ` Matthieu Moy
2011-03-28 18:57                 ` demerphq
2011-03-28 19:12                   ` Andrew Garber
2011-03-28 19:40                     ` Matthieu Moy
2011-03-28 20:12                       ` Andrew Garber
2011-03-28 20:25                         ` Jeff King
2011-03-28 21:25                           ` Jeff King
2011-03-28 20:37                         ` Matthieu Moy
2011-03-29 10:54                   ` Andreas Ericsson
2011-05-22 19:41 ` Michael Witten

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=4D908170.2020207@lyx.org \
    --to=vfr@lyx.org \
    --cc=avarab@gmail.com \
    --cc=git@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.