linux-kernel - Re: [git pull] lguest: paravirt boot code

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:	Tue, 23 Oct 2007 16:37:08 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Rusty Russell <rusty@...tcorp.com.au>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, lguest <lguest@...abs.org>,
	virtualization@...ts.linux-foundation.org,
	Jeremy Fitzhardinge <jeremy@...p.org>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [git pull] lguest: paravirt boot code

Linus Torvalds wrote:
> 
> On Tue, 23 Oct 2007, Rusty Russell wrote:
>> Well, with that out the way, and some scatterlist fixups, please pull from
>>
>> 	git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux-2.6-lguest.git

Also, please add a "lguest: " prefix to all future commits.

Otherwise, in the one-line summary, it is impossible to tell what 
portion of the kernel is being updated:

	Use "struct boot_params" in example launcher
	Loading bzImage directly.
	Rename "cr3" to "gpgdir" to avoid x86-specific naming.
	Pagetables to use normal kernel types
	Move register setup into i386_core.c
	Accept elf files that are valid but have sections that can not
		be mmap'ed for some reason.

git tools are all keyed to use that first line as a summary of the 
changeset, without giving any other context whatsoever.  See Linus's 
2.6.X-rcY announcements, for example.

This is also described in akpm's 
http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt or my 
http://linux.yyz.us/patch-format.html

	Jeff


-
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/