From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 66963] Rv6xx dpm problems Date: Tue, 07 Jul 2015 21:45:28 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1610886405==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 2F4CC6EA8B for ; Tue, 7 Jul 2015 14:45:29 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1610886405== Content-Type: multipart/alternative; boundary="1436305528.4Ba615AD8.32608"; charset="UTF-8" --1436305528.4Ba615AD8.32608 Date: Tue, 7 Jul 2015 21:45:28 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=66963 --- Comment #282 from Kajzer --- (In reply to Alex Deucher from comment #280) > You don't need to start the bisect again. `git bisect reset` will clean up > the bisect and reset your current HEAD to where it was when started the > bisect. At that point just run `git reset --hard > 77497f2735ad6e29c55475e15e9790dbfa2c2ef8` or 'git checkout -b testing > 77497f2735ad6e29c55475e15e9790dbfa2c2ef8` to checkout the specific commit > you want to test. The second method creates a new branch called testing > with HEAD set to the specified commit. The reset command resets the HEAD of > the current tree to the specified commit. I'm running now on kernel compiled with first method, if previous bisect was indeed done right I don't expect dpm freeze. Anyway, thanks for the second method, if I understood you correctly, basically I can test if Michel's commit is bad or not by running : $ git bisect reset $ git checkout -b testing 02376d8282b88f07d0716da6155094c8760b1a13 Of course after I'm done with current test. Please correct me if I'm wrong. -- You are receiving this mail because: You are the assignee for the bug. --1436305528.4Ba615AD8.32608 Date: Tue, 7 Jul 2015 21:45:28 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 282 on bug 66963 from 
(In reply to Alex Deucher from comment #280)
> You don't need to start the bisect again.  `git bisect reset` will clean up
> the bisect and reset your current HEAD to where it was when started the
> bisect.  At that point just run `git reset --hard
> 77497f2735ad6e29c55475e15e9790dbfa2c2ef8` or 'git checkout -b testing
> 77497f2735ad6e29c55475e15e9790dbfa2c2ef8` to checkout the specific commit
> you want to test.  The second method creates a new branch called testing
> with HEAD set to the specified commit.  The reset command resets the HEAD of
> the current tree to the specified commit.

I'm running now on kernel compiled with first method, if previous bisect was
indeed done right I don't expect dpm freeze.

Anyway, thanks for the second method, if I understood you correctly, basically
I can test if Michel's commit is bad or not by running :
$ git bisect reset
$ git checkout -b testing 02376d8282b88f07d0716da6155094c8760b1a13

Of course after I'm done with current test.
Please correct me if I'm wrong.

You are receiving this mail because:
  • You are the assignee for the bug.
--1436305528.4Ba615AD8.32608-- --===============1610886405== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============1610886405==--