All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Askar Safin <safinaskar@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: https://github.com/rust-lang/rust is not bisectable
Date: Sat, 17 Dec 2022 17:34:07 +0100	[thread overview]
Message-ID: <878rj6rnuo.fsf@igel.home> (raw)
In-Reply-To: <CAPnZJGABhczzs-6Pri2SAOkujJXT1+JDH9FiwdDns6=miZmvFQ@mail.gmail.com> (Askar Safin's message of "Sat, 17 Dec 2022 19:00:49 +0300")

On Dez 17 2022, Askar Safin wrote:

> Okay, so "git bisect" gave us commit
> 26562973b3482a635416b2b663a13016d4d90e20. And here I see a bug:
> 7175c499ecc32cb3ff713be0bbac9fd12990a34e is NOT ancestor of
> 26562973b3482a635416b2b663a13016d4d90e20!

26562973b3482a635416b2b663a13016d4d90e20 is an ancestor of the bad
commit, and not an ancestor of the good commit, thus it is a candidate
for introducing the bad condition.  In a non-linear history, there can
be multiple good commits that are not directly related, each one cutting
out branches from the history.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."

  reply	other threads:[~2022-12-17 16:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-17 16:00 https://github.com/rust-lang/rust is not bisectable Askar Safin
2022-12-17 16:34 ` Andreas Schwab [this message]
2022-12-18  3:15   ` Askar Safin
2022-12-18  9:16     ` Andreas Schwab
2022-12-18  9:37     ` SZEDER Gábor
2022-12-18 10:03       ` Askar Safin
2022-12-18 10:25         ` Andreas Schwab
2022-12-18 10:52         ` SZEDER Gábor
2022-12-18 14:10           ` rsbecker

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=878rj6rnuo.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=git@vger.kernel.org \
    --cc=safinaskar@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 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.