From: Gregory Heytings <gregory@heytings.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: "Gerd Möllmann" <gerd.moellmann@gmail.com>, emacs-devel@gnu.org
Subject: Re: Emacs git repo mangled
Date: Tue, 01 Nov 2022 19:41:41 +0000 [thread overview]
Message-ID: <48c054670fab42fe2218@heytings.org> (raw)
In-Reply-To: <87o7tqbiqv.fsf@gmx.de>
>> Eglot's merge (0186faf2a1) is the first case in Emacs' history in which
>> another root commit (1e5b753bf4) was added to the repository. So at the
>> moment there is only one such command to type when starting a
>> bisection: git bisect good 806734c1b1.
>
> Wouldn't his mean that all other commits prior the eglot merge would be
> regarded as "good", when bisecting? I doubt this is what we want.
>
No, it means that all commits between Eglot's root (1e5b753bf4) and
Eglot's merge (0186faf2a1), except Eglot's merge itself, are regarded as
"good". IOW, git bisect will never "descend" into Eglot's branch, and
only into that branch, which is exactly what we want.
next prev parent reply other threads:[~2022-11-01 19:41 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 9:50 Emacs git repo mangled 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2022-10-31 15:25 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
2022-10-31 21:15 ` Andreas Schwab
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=48c054670fab42fe2218@heytings.org \
--to=gregory@heytings.org \
--cc=emacs-devel@gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=michael.albinus@gmx.de \
/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.