public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paolo Ornati <ornati@gmail.com>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: linux-kernel@vger.kernel.org, "Ted Ts'o" <tytso@mit.edu>
Subject: Re: help with git bisecting a bug 16376: random - possibly Radeon DRM KMS related - freezes
Date: Sun, 5 Sep 2010 14:20:31 +0200	[thread overview]
Message-ID: <20100905142031.4b692ed5@gmail.com> (raw)
In-Reply-To: <201009050953.52440.Martin@lichtvoll.de>

On Sun, 5 Sep 2010 09:53:41 +0200
Martin Steigerwald <Martin@lichtvoll.de> wrote:

> I am also seeking help with selecting more suitable commits to test: If 
> its a Radeon KMS related freeze and everything points at it, I think the 
> offending commit is in the first quarter of what git commit shows to me[2]. 
> Thus I'd  like to select one commit before those drm/kms related commits 
> and one after it, before testing any other commits.

If you "know better" than git-bisect and want to test a particular
commit, just do:

	git reset --hard commit_id

-- 
	Paolo Ornati
	Linux 2.6.35.4 on x86_64

  reply	other threads:[~2010-09-05 12:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-31 19:53 help with git bisecting a bug 16376: random - possibly Radeon DRM KMS related - freezes Martin Steigerwald
2010-08-31 22:39 ` Ken Moffat
2010-09-01 16:10   ` Martin Steigerwald
2010-09-01 18:13     ` Ken Moffat
2010-09-01 18:47 ` Paolo Ornati
2010-09-01 19:26   ` Martin Steigerwald
2010-09-05  7:53   ` Martin Steigerwald
2010-09-05 12:20     ` Paolo Ornati [this message]
2010-09-05 13:25       ` Martin Steigerwald
2010-09-07  2:51     ` Ted Ts'o
2010-09-09 14:18       ` Martin Steigerwald
2010-09-10 11:55         ` Florian Mickler
2010-09-10 13:49           ` Martin Steigerwald
2010-09-10 15:53             ` Theodore Tso
2010-09-10 16:18               ` Martin Steigerwald

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=20100905142031.4b692ed5@gmail.com \
    --to=ornati@gmail.com \
    --cc=Martin@lichtvoll.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox