All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Sixt <j.sixt@viscovery.net>
To: "Arkadiusz Miśkiewicz" <arekm@maven.pl>
Cc: git@vger.kernel.org
Subject: Re: is smarter bisect possible?
Date: Fri, 25 Sep 2009 09:59:33 +0200	[thread overview]
Message-ID: <4ABC7865.7010705@viscovery.net> (raw)
In-Reply-To: <h9hrv3$cao$1@ger.gmane.org>

Arkadiusz Miśkiewicz schrieb:
> I have such problem. Linus kernel tree merged some feature 
> (94e0fb086fc5663c38bbc0fe86d698be8314f82f) that was developed in .31rc9 era.
> 
> Current Linus kernel tree with that feature merged shows some regression. 
> Tree just before that merge doesn't show regression.
> 
> Now if I start to bisect just that feature (good 
> b7f21bb2e23b4fec16b448a34889f467465be659, bad 
> 94e0fb086fc5663c38bbc0fe86d698be8314f82f) then git gets me whole tree back 
> to .31rc9 era which... doesn't show any problems.
> 
> This means that only combined current Linus tree and that feature shows a 
> problem.

Try this:

http://www.kernel.org/pub/software/scm/git/docs/user-manual.html#bisect-merges

-- Hannes

      reply	other threads:[~2009-09-25  7:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-25  9:37 is smarter bisect possible? Arkadiusz Miśkiewicz
2009-09-25  7:59 ` Johannes Sixt [this message]

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=4ABC7865.7010705@viscovery.net \
    --to=j.sixt@viscovery.net \
    --cc=arekm@maven.pl \
    --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.
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.