From: Christian Couder <christian.couder@gmail.com>
To: Harald Nordgren <haraldnordgren@gmail.com>
Cc: Stefan Beller <sbeller@google.com>, git <git@vger.kernel.org>,
Tiago Botelho <tiago@gitlab.com>
Subject: Re: [PATCH] Create '--merges-only' option for 'git bisect'
Date: Thu, 12 Apr 2018 10:58:21 +0200 [thread overview]
Message-ID: <CAP8UFD3j-MGY7jHQK52zVLYMB=1vhCSFKxrvQ1JsRW-Rmnn8Qg@mail.gmail.com> (raw)
In-Reply-To: <CAHwyqnVg83xSQHRnDVz+aMxPPMj-3bWF4P8YUxEjurxnpDhFEQ@mail.gmail.com>
On Thu, Apr 12, 2018 at 9:49 AM, Harald Nordgren
<haraldnordgren@gmail.com> wrote:
> I think it looks similar. But if I'm reading that thread correctly
> then there was never a patch created, right?
(It is customary on this mailing list to reply after the sentences we
reply to. We don't "top post".)
On the GSoC idea pages (like https://git.github.io/SoC-2018-Ideas/) we
have been suggesting "Implement git bisect --first-parent" and there
are the following related links:
https://public-inbox.org/git/20150304053333.GA9584@peff.net/
https://public-inbox.org/git/4D3CDDF9.6080405@intel.com/
Tiago in Cc also tried at a recent London hackathon to implement it
and came up with the following:
https://github.com/tiagonbotelho/git/pull/1/files
I tried to help him by reworking his commit in the following branch:
https://github.com/chriscool/git/commits/myfirstparent
next prev parent reply other threads:[~2018-04-12 8:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 22:55 [PATCH] Create '--merges-only' option for 'git bisect' Harald Nordgren
2018-04-11 23:33 ` Stefan Beller
2018-04-12 7:49 ` Harald Nordgren
2018-04-12 8:58 ` Christian Couder [this message]
2018-04-12 9:27 ` Tiago Botelho
2018-04-12 11:53 ` Johannes Schindelin
2018-04-12 12:19 ` Tiago Botelho
2018-04-30 11:31 ` Johannes Schindelin
2018-04-30 11:34 ` Tiago Botelho
2018-05-01 11:31 ` Johannes Schindelin
2018-04-12 11:35 ` Johannes Schindelin
2018-04-12 11:33 ` Johannes Schindelin
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAP8UFD3j-MGY7jHQK52zVLYMB=1vhCSFKxrvQ1JsRW-Rmnn8Qg@mail.gmail.com' \
--to=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=haraldnordgren@gmail.com \
--cc=sbeller@google.com \
--cc=tiago@gitlab.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).