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:	Mon, 26 Oct 2009 20:30:03 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	David Miller <davem@...emloft.net>
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

On Mon, 2009-10-26 at 17:15 -0700, David Miller wrote:

> What you can't do is _PUBLISH_ this anywhere to a tree that people
> also do development against _UNTIL_ you get those acks and tested-by
> tags back from people.
> 
> Once your acks etc. come in, you can pop all of those pending patches
> out of your tree, add the ack tags to the commit messages, then
> reapply them.
> 
> Then you can push to your public tree, but no sooner.
> 
> It really is that simple.

But you never answered my question? How long do you let it cook? I don't
have regular people that test my patches and pass tested by, whatever. I
get them here and there, sometimes I even a reviewed by.  Most of the
time I just get silence.

My testing is mostly done in Ingo's test suite, and that happens after I
do my push to him. This works best for me.

Perhaps this doesn't bother your work flow, but it does mine. 90% (or
more) of the bugs in my code is found in Ingo's test suites. This means
I want to get it to him ASAP, and I do so by pushing it to him and
Cc'ing LKML. Then I can work on my next set of patches without worrying
about the last set I sent.

If I had to publish and let cook on LKML, then I would also need to keep
better accounting of what I have pushed out and what I have left to do.
My wife does the bills because I can't do accounting for crap. If I need
to account for patches that have been to LKML, and time them to know
when to push into some tree, I'm just destine to let a few patches slip
through the cracks.

-- Steve

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