all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: Emacs git repo mangled
Date: Mon, 31 Oct 2022 22:10:35 +0100	[thread overview]
Message-ID: <87mt9bekzm.fsf@telefonica.net> (raw)
In-Reply-To: <jwvleovzq5j.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 31 Oct 2022 16:39:12 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> Andreas Schwab [2022-10-31 19:33:13] wrote:
>> On Okt 31 2022, Stefan Monnier wrote:
>>> Nothing's wrong: the Git history looks fine to me.
>>> The problem is fundamental to `git bisect` (which starts from the
>>> assumption that the history is linear, which is a lie).
>> That's not true.  Bisection handles nonlinear history very well.
>
> I did not say it doesn't handle nonlinear history well.  I said it
> assumes that the history is linear (it's inherent to the notion of
> "bisecting").

Not at all. See "Bisection algorithm discussed" in [1]. `git bisect'
would be very dumb if it wouldn't take advantage of merge commits.

As for bisecting Emacs, it's a real PITA because there are so many
broken commits plus you really need a full rebuild for each step to
avoid false results.

One thing that would be useful is a list of bad commits on a format that
could be easily used with `git bisect skip'.

1. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-bisect-lk2009.html




  reply	other threads:[~2022-10-31 21:10 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 15:25 Emacs git repo mangled Payas Relekar
2022-10-31 16:11 ` João Távora
2022-10-31 16:48   ` Michael Albinus
2022-10-31 17:57   ` Stefan Monnier
2022-10-31 18:33     ` Andreas Schwab
2022-10-31 20:39       ` Stefan Monnier
2022-10-31 21:10         ` Óscar Fuentes [this message]
2022-10-31 21:15         ` Andreas Schwab
  -- strict thread matches above, loose matches on Subject: below --
2022-10-31  9:50 Michael Albinus
2022-10-31 13:09 ` Gerd Möllmann
2022-10-31 16:43   ` Michael Albinus
2022-11-01  5:44     ` Gerd Möllmann
2022-11-01  9:15       ` Michael Albinus
2022-11-01  9:28         ` Gerd Möllmann
2022-11-01 12:07         ` Gregory Heytings
2022-11-01 13:32           ` Michael Albinus
2022-11-01 13:55             ` Gregory Heytings
2022-11-01 15:23               ` Michael Albinus
2022-11-01 16:47                 ` Gregory Heytings
2022-11-01 17:19                   ` Eli Zaretskii
2022-11-01 18:25                     ` Gregory Heytings
2022-11-02  5:51                       ` Gerd Möllmann
2022-11-02  9:26                         ` Gregory Heytings
2022-11-01 19:02                   ` Michael Albinus
2022-11-01 19:41                     ` Gregory Heytings
2022-11-02  3:26                       ` Eli Zaretskii
2022-11-02  9:14                         ` Gregory Heytings
2022-11-02 12:59                           ` Phil Sainty
2022-11-02 13:10                             ` Gregory Heytings
2022-11-02 13:49                           ` Eli Zaretskii
2022-11-02 14:27                             ` Gregory Heytings
2022-11-05 10:54                       ` Michael Albinus
2022-11-05 21:58                         ` Gregory Heytings
2022-11-02  2:11                   ` Phil Sainty
2022-11-02 10:56                     ` Robert Pluim
2022-10-31 13:38 ` Andreas Schwab
2022-10-31 16:45   ` Michael Albinus
2022-10-31 15:35 ` João Távora
2022-10-31 16:04   ` Stefan Kangas
2022-10-31 16:24     ` João Távora
2022-10-31 17:28       ` Stefan Kangas
2022-10-31 21:45 ` Gregory Heytings

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=87mt9bekzm.fsf@telefonica.net \
    --to=ofv@wanadoo.es \
    --cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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.