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  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, 27 Oct 2009 13:18:34 -0400 (EDT)
From:	Nicolas Pitre <nico@...xnic.net>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Ingo Molnar <mingo@...e.hu>, Sam Ravnborg <sam@...nborg.org>,
	LKML <linux-kernel@...r.kernel.org>,
	"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

On Tue, 27 Oct 2009, Steven Rostedt wrote:

> 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.
>
[...]
> 
> My suggestion is to add an "annotation" commit that can tag another
> commit with something like a "tested-by". This way a tester can say,
> they tested this particular commit, and if someone changes it, the SHA1
> will no longer match. And then we can also have a record of what commit
> was tested by who, after the fact that it went into git.

There is a "git notes" feature from Johan Herland being carried in thepu 
branch of the git repository.  I strongly suggest to those who might 
think this could be useful in this context to express their interest by 
posting to git@...r.kernel.org.  With a concrete need and usage scenario 
(and offer to help at least with testing) this feature might become 
usable sooner.


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

Powered by blists - more mailing lists