linux-kernel - Re: [RFC] to rebase or not to rebase on 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:	Wed, 28 Oct 2009 07:40:09 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Sam Ravnborg <sam@...nborg.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Nicolas Pitre <nico@...xnic.net>,
	"Luck, Tony" <tony.luck@...el.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	"Luis R. Rodriguez" <mcgrof@...il.com>,
	Jeff Garzik <jeff@...zik.org>,
	Robert Richter <robert.richter@....com>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Jean Delvare <khali@...ux-fr.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	"David S. Miller" <davem@...emloft.net>
Subject: Re: [RFC] to rebase or not to rebase on linux-next


* Steven Rostedt <rostedt@...dmis.org> wrote:

> On Tue, 2009-10-27 at 08:59 +0100, Ingo Molnar wrote:
> 
> > For any reasonably complex change you simply need to wait a bit 
> > anyway to gather feedback. And for trivial/obvious/small patches it 
> > makes little sense to upset the Git history just to add the tags.
> > 
> > (And if there's frequent problems with small changes that were 
> > supposed to be easy you need to revisit the quality process.)
> 
> Sure, but I'm not talking about changing the patch, I'm talking about 
> a late "reviewed by" or "tested-by". These usually do come after a 
> patch set has been moved into the final git push. It would be nice to 
> flag a commit that it was tested by someone.

If you want to make your patches dependent on acks then you first need 
to send out those patches with an '[RFC]' added, and put into a branch 
hierarchy (rfc/* would be fine) that i sure wont pull from you.

You can also send obvious/small/own patches out for immediate pull. In 
that case extra review can still be done after you sent patches out. 
Mistakes noticed during review will be credited in terms of future 
Reported-by tags.

People do this frequently.

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