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] [day] [month] [year] [list]
Date:	Wed, 28 Oct 2009 11:15:57 -0400
From:	Steven Rostedt <>
To:	Nicolas Pitre <>
Cc:	Ingo Molnar <>, Sam Ravnborg <>,
	LKML <>,
	"Luck, Tony" <>,
	Stephen Rothwell <>,
	"Luis R. Rodriguez" <>,
	Jeff Garzik <>,
	Robert Richter <>,
	Dmitry Torokhov <>,
	Jean Delvare <>,
	Linus Torvalds <>,
	"David S. Miller" <>
Subject: Re: [RFC] to rebase or not to rebase on linux-next

On Tue, 2009-10-27 at 13:18 -0400, Nicolas Pitre wrote:
> 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  With a concrete need and usage scenario 
> (and offer to help at least with testing) this feature might become 
> usable sooner.

Thanks for the pointer Nicolas, but it looks like my ideas have already
been NAK'd by Linus.

Oh well,

-- Steve

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists