From: Hagen Paul Pfeifer <hagen@jauu.net>
To: git@vger.kernel.org
Subject: Bisect limited to Merge Commits
Date: Wed, 27 Apr 2016 22:45:51 +0200 [thread overview]
Message-ID: <20160427204551.GB4613@virgo.localdomain> (raw)
Hey,
are there any plans to add an option to skip all non-merge commits via
bisecting?
git bisect start --merges-only
Imagine a "rebase feature branch" style of development. All features are
developed on separate features branch which are rebased on master and
immediately merged into the upstream master. Now think about lazy programmers
who miss to check the build process at each commit - leading to many
unbuildable commits. The only guaranteed buildable commit is often the merge
commit.
Bisecting only merge commits will reduce the amount of skip commands (think
about many unbuildable commits) and reduce the number of tests.
Any comments on this idea? What about extending bisect.c:do_find_bisection()
hgn
next reply other threads:[~2016-04-27 20:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 20:45 Hagen Paul Pfeifer [this message]
2016-04-27 20:56 ` Bisect limited to Merge Commits Junio C Hamano
2016-04-27 21:33 ` Johannes Sixt
2016-04-27 22:25 ` Junio C Hamano
2016-04-28 6:19 ` Hagen Paul Pfeifer
2016-04-28 6:44 ` Jacob Keller
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=20160427204551.GB4613@virgo.localdomain \
--to=hagen@jauu.net \
--cc=git@vger.kernel.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 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).