linux-kernel - Re: My kernel hangs again: Help with git please

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 15 Jun 2007 20:33:38 -0400 (EDT)
From:	Daniel Barkalow <barkalow@...ervon.org>
To:	Carlo Wood <carlo@...noe.com>
cc:	linux-kernel@...r.kernel.org
Subject: Re: My kernel hangs again: Help with git please

On Sat, 16 Jun 2007, Carlo Wood wrote:

> Therefore I have the following questions:
> 
> 1) What git command will ASSURE that I get the LATEST
>    kernel tree checked out?
>
> I tried this:
> 
> hikaru:/usr/src/kernel/git/linux-2.6>git branch -l
> * bisect
>   master
>   origin
> hikaru:/usr/src/kernel/git/linux-2.6>git reset --hard HEAD

HEAD doesn't mean what you think it means. It's the latest revision on the 
branch with the *. What you want is:

$ git checkout master

This will move the * to "master", which shouldn't have been affected by 
any of this, and move your working directory to this point as well. At 
that point, you should be able to build a working kernel.

What "git reset --hard HEAD" does is discard any differences to tracked 
files between your working directory and the revision you're on. It's 
relevant if you want to discard local changes, not otherwise.

	-Daniel
*This .sig left intentionally blank*
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/