From: Junio C Hamano <gitster@pobox.com>
To: Olliver Schinagl <oliver@schinagl.nl>
Cc: git@vger.kernel.org,
Christian Couder <christian.couder@gmail.com>,
Stefan Haller <lists@haller-berlin.de>
Subject: Re: [RFC] bisect: Introduce skip-when to automatically skip commits
Date: Sat, 06 Apr 2024 10:07:49 -0700 [thread overview]
Message-ID: <xmqq1q7il8re.fsf@gitster.g> (raw)
In-Reply-To: <b194ba7c-454b-494f-bef2-e9eac7ca87f1@schinagl.nl> (Olliver Schinagl's message of "Sat, 6 Apr 2024 12:06:25 +0200")
Olliver Schinagl <oliver@schinagl.nl> writes:
> But seeing that these are your main concerns, I'm more confident I'm
> not completly on the wrong path here.
Mind you that they are not "MAIN" concerns. They were the ones that
jumped out at me from your sketch. After seeing the real thing, I
may find completely different issues that I could have spotted in
this version as well---it is natural that people notice things they
did not initially notice with a richer context.
next prev parent reply other threads:[~2024-04-06 17:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-30 8:10 [RFC] bisect: Introduce skip-when to automatically skip commits Olliver Schinagl
2024-04-05 6:50 ` Olliver Schinagl
2024-04-06 1:08 ` Junio C Hamano
2024-04-06 10:06 ` Olliver Schinagl
2024-04-06 13:50 ` Phillip Wood
2024-04-06 19:17 ` Olliver Schinagl
2024-04-07 14:09 ` phillip.wood123
2024-04-07 14:52 ` Olliver Schinagl
2024-04-07 15:12 ` phillip.wood123
2024-04-07 21:11 ` Olliver Schinagl
2024-04-08 16:49 ` Junio C Hamano
2024-04-10 10:39 ` Olliver Schinagl
2024-04-10 16:47 ` Junio C Hamano
2024-04-10 19:22 ` Olliver Schinagl
2024-04-10 19:31 ` Junio C Hamano
2024-04-10 19:39 ` Olliver Schinagl
2024-04-12 13:35 ` Phillip Wood
2024-04-06 17:07 ` Junio C Hamano [this message]
2024-04-06 19:19 ` Olliver Schinagl
2024-04-06 10:22 ` Olliver Schinagl
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=xmqq1q7il8re.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=lists@haller-berlin.de \
--cc=oliver@schinagl.nl \
/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).