linux-kernel - Re: [GIT PULL] notification: including fanotify

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]

Message-ID: <alpine.LFD.2.00.1002271531520.4513@localhost.localdomain>
Date:	Sat, 27 Feb 2010 15:38:32 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
cc:	Eric Paris <eparis@...hat.com>, viro@...iv.linux.org.uk,
	hch@...radead.org, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] notification: including fanotify

On Sun, 28 Feb 2010, Stephen Rothwell wrote:
> 
> You also forgot to mention that this whole tree has been rebased since
> (my) Friday and the version of the above commit in linux-next does not
> have that hunk.

Yeah. This is why I hate people who rebase too much. 

I don't mind rebases per se, but when they happen within the last few 
days, it just tells me that "that tree got no testing". 

So guys: feel free to rebase. But when you do, wait a week afterwards. 
Don't "rebase and ask Linus to pull". That's just _wrong_. It means that 
the tree you asked me to pull has gotten zero testing.

And sometimes that lack of testing is more obvious than other times. In 
this case, it was pretty damn obvious.

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