linux-kernel - Re: git trees which are not yet in linux-next

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Mon, 5 May 2008 10:18:31 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	Jeff Garzik <jeff@...zik.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-next@...r.kernel.org, sfrench@...ibm.com,
	swhiteho@...hat.com, ralf@...ux-mips.org, drzeus-list@...eus.cx,
	jack@....cz, cbou@...l.ru, jens.axboe@...cle.com, ericvh@...il.com,
	wim@...ana.be, chris@...kel.net, nico@....org,
	penberg@...helsinki.fi, clameter@....com, ezk@...sunysb.edu,
	linux-kernel@...r.kernel.org
Subject: Re: git trees which are not yet in linux-next

On Sat, 03 May 2008 10:46:39 +0200 Stefan Richter <stefanr@...6.in-berlin.de> wrote:
>
> Of course some committers have more than one tree in -next.  So if 
> Andrew wants to know the actual tree, the laziest method which I know of is
> $ gitk <commit_id>
> 
> Among else, gitk shows which branches contain the commit.  (How to do 
> this without X GUI?)

Unfortunately, this will not work either as I do not export to the public
tree the heads of each of the branches that I merge.  It does work in my
tree until I do the next update.

However, if you look at the closest following merge that is committed by
me, that will tell you which branch the commit was on.

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped