All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Sixt <j6t@kdbg.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Lutomirski <luto@mit.edu>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	git@vger.kernel.org
Subject: Re: AAARGH bisection is hard (Re: [2.6.39 regression] X locks up hard right after logging in)
Date: Thu, 12 May 2011 20:54:53 +0200	[thread overview]
Message-ID: <4DCC2CFD.4010807@kdbg.org> (raw)
In-Reply-To: <BANLkTi=YDZa+BRaG90vJsjrT9VxgySrDRQ@mail.gmail.com>

Am 12.05.2011 19:37, schrieb Linus Torvalds:
> If you think it's networking, for example, and you've bisected into
> there but aren't sure, do "gitk --bisect", find the point where I
> merge, and pick that (and my parent), and "git bisect reset" those
> points.

Except that you should git reset --hard; git bisect reset gets you out
of bisect-mode, no?

-- Hannes

  reply	other threads:[~2011-05-12 19:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-12 17:15 AAARGH bisection is hard (Re: [2.6.39 regression] X locks up hard right after logging in) Andrew Lutomirski
2011-05-12 17:37 ` Linus Torvalds
2011-05-12 18:54   ` Johannes Sixt [this message]
2011-05-12 19:17     ` Linus Torvalds
2011-05-13 13:39   ` Andrew Lutomirski
2011-05-13  8:20 ` Christian Couder
2011-05-13 13:38   ` Andrew Lutomirski
2011-05-13 14:56     ` Andrew Lutomirski
2011-05-13 16:11       ` Linus Torvalds
2011-05-13 16:13         ` Andrew Lutomirski
2011-05-13 17:24         ` Andrew Lutomirski
2011-05-13 17:54           ` Linus Torvalds
2011-05-13 18:34             ` Johannes Sixt
2011-05-13 18:41               ` Linus Torvalds
2011-05-13 18:47                 ` Johannes Sixt
2011-05-13 18:48                 ` Junio C Hamano
2011-05-13 18:55                   ` Andrew Lutomirski
2011-05-13 19:18                   ` Linus Torvalds

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=4DCC2CFD.4010807@kdbg.org \
    --to=j6t@kdbg.org \
    --cc=git@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@mit.edu \
    --cc=netdev@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.