On Wed, Apr 27, 2016 at 11:19 PM, Hagen Paul Pfeifer wrote:
> * Johannes Sixt | 2016-04-27 23:33:53 [+0200]:
>
> Hey Junio, hey Hannes,
>
>> git bisect start
>> git rev-list --first-parent --boundary origin..origin/pu |
>> sed -ne s/-//p | xargs git bisect good
>> git bisect bad origin/pu
>>
>>a
* Johannes Sixt | 2016-04-27 23:33:53 [+0200]:
Hey Junio, hey Hannes,
> git bisect start
> git rev-list --first-parent --boundary origin..origin/pu |
> sed -ne s/-//p | xargs git bisect good
> git bisect bad origin/pu
>
>and it starts bisecting among the 50-something first-parent commits betwee
Johannes Sixt writes:
> Am 27.04.2016 um 22:56 schrieb Junio C Hamano:
>> So being able to stop at only commits on the first-parent chain is a
>> valid and useful tool. "git bisect --first-parent" is one of the
>> things that are sometimes asked for.
>
> With origin pointing to git.git, I attemp
Am 27.04.2016 um 22:56 schrieb Junio C Hamano:
So being able to stop at only commits on the first-parent chain is a
valid and useful tool. "git bisect --first-parent" is one of the
things that are sometimes asked for.
With origin pointing to git.git, I attempted this:
git bisect start
git r
Hagen Paul Pfeifer writes:
> 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.
I do not want to imagine such ;-) The only semi-sensible reason why
peopl
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 upstrea
6 matches
Mail list logo
