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 18:34:16 -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 20:30:03 -0400

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

1 day, maybe 2 or even 3 depending upon the type of change and the
travel schedules of core developers.  On the networking lists things
get tested and reviewed quite quickly.

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

So you both should keep your trees private until it's all sorted out
and you have the results in hand.

Nobody forces you guys to use public trees just to run Ingo's personal
test suite, you have decided to work that way.  And that is therefore
something you guys can change without effecting other people.

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

The problem isn't that you have to push patches out and only work
with patches, the problem is that you want to use publicly visible
GIT trees to do your testing at all times.

And sorry, that is not how you're supposed to do things.
--
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/