On Mon, 2011-01-10 at 12:14 +1030, Arthur Marsh wrote:
> This problem still occurs on kernel 2.6.37-git4.
>
> Is there a way to do a git-bisect when a particular commit is removed?
>
> When I did a
>
> git reset --hard v2.6.37
> git revert 541cc966915b6756e54c20eebe60ae957afdb537
>
> and rebui
This problem still occurs on kernel 2.6.37-git4.
Is there a way to do a git-bisect when a particular commit is removed?
When I did a
git reset --hard v2.6.37
git revert 541cc966915b6756e54c20eebe60ae957afdb537
and rebuilt the kernel I still had the problem, indicating that some
other commit i
Julien Cristau wrote, on 08/01/11 22:38:
On Sat, Jan 8, 2011 at 22:28:46 +1030, Arthur Marsh wrote:
Thanks, could you give me the git commands to re-base on 2.6.37 then revert that
commit? I'll then be able to give it a try.
git reset --hard v2.6.37
git revert 541cc966915b6756e54c20eebe60a
On Sat, Jan 8, 2011 at 22:28:46 +1030, Arthur Marsh wrote:
> Thanks, could you give me the git commands to re-base on 2.6.37 then revert
> that
> commit? I'll then be able to give it a try.
>
git reset --hard v2.6.37
git revert 541cc966915b6756e54c20eebe60ae957afdb537
Cheers,
Julien
sign
4 matches
Mail list logo
