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:	Mon, 26 Oct 2009 16:30:50 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	rostedt@...dmis.org
Cc:	sam@...nborg.org, mingo@...e.hu, linux-kernel@...r.kernel.org,
	nico@...xnic.net, tony.luck@...el.com, sfr@...b.auug.org.au,
	mcgrof@...il.com, jeff@...zik.org, robert.richter@....com,
	dmitry.torokhov@...il.com, khali@...ux-fr.org,
	torvalds@...ux-foundation.org
Subject: Re: [RFC] to rebase or not to rebase on linux-next

From: Steven Rostedt <rostedt@...dmis.org>
Date: Mon, 26 Oct 2009 19:26:28 -0400

> I think this is more of a failure in git than in the work flow we
> present.

Others (like me) will say you should have let that patch cook for a
while on the mailing list or in your tree before publishing, in order
to let those acks and tested-by replies come in.

That's how I handle this.

And I really don't buy the argument that you have to publish the
change in a GIT tree to get those ACKs and tested-by replies.
--
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