> > I'm rather new to all this and still (to some extent) trying to
figure
quoted text
> > out what is expected.
> 
> We're all still trying to figure it out, really.  We've gone and made
it
quoted text
> awfully easy to get code into the kernel nowadays.  Perhaps too easy.
I'm
quoted text
> presently having a little campaign of watching what's going on a bit
more
quoted text
> closely, and ecouraging people to make it easier for others to see
what's
quoted text
> going on, should they choose to do so.
> 
> I'm hoping that by the time we're developing 2.6.26 there will be a
unified
quoted text
> git tree (aka linux-next) (basically all the git and quilt trees from
-mm)
quoted text
> for people to look at and play with.  That'll improve our pre-merge
test
quoted text
> coverage, but won't do much to improve review.  And it won't do
anything to
quoted text
> improve our post-merge bugfixing.

All of them are good, but I trust testing and sparse more than review..
:)

quoted text
> > Maybe what is needed is git pull --ack?
> 
> I'm also hoping/expecting/planning that if someone tries to merge a
patch
quoted text
> into mainline, and that patch hasn't been in linux-next for "long
enough",
quoted text
> flags will wave and lights will flash and we can get to take a closer
look
quoted text
> at why it was so late and whether it's OK.

Hmm...  what if git told you what time the original git commit happened?
That can't be that hard to add (if it's not already there!)

Steve


--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/