linux-kernel - Re: [GIT PATCH] PCI patches for 2.6.24-rc1

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, 6 Nov 2007 11:14:06 -0500
From:	Theodore Tso <tytso@....edu>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Greg KH <gregkh@...e.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-pci@...ey.karlin.mff.cuni.cz,
	pcihpd-discuss@...ts.sourceforge.net
Subject: Re: [GIT PATCH] PCI patches for 2.6.24-rc1

On Mon, Nov 05, 2007 at 02:16:05PM -0800, Linus Torvalds wrote:
> 
> 
> On Mon, 5 Nov 2007, Linus Torvalds wrote:
> > 
> > This one is bogus:
> 
> Side note: I pulled and pushed out, since I assume the *code* is correct, 
> but please double-check the commit messages for things like this.
> 
> gitk makes it really easy, since it will highlight valid commit ID's. It 
> looks lik eyou may have re-ordered the commits or something?

hmm, I wonder if it would be a good idea to put together a git hook
script that looks for things that look like git commit ID's, and if
they aren't valid commit ID's that appear in the repository, the
maintainer gets a warning when they do a "git am" or otherwise suck in
a patch that was sent via e-mail...

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