I was thinking more of just sharing the code. There are more trees out
there than just Linus'. Deciding to apply one of your patches is much
easier if we have the specific patch, rather than just a 600k patch from
Linus that happens to include your patch buried inside it.
> If people think that this will help with development of the stuff I work with,
> please say so.
>
> Patches that touches the networking core, etc, I post to netdev, and not here,
> and this is done by lots of other people, for several subsystems, and
> contributes to the feeling that things are not being posted to lkml. They are
> not, never had, nothing new, only BK has a license people disagree with and all
> of a sudden is the reason for patches not being more reviewed, etc. I beg to
> disagree.
I'm not bitching about bk here. It's clearly improved Linus'
productivity. I don't use it, but I like Linus using it. And with
the udiff-ing of each changeset, I can see each patch he applied, even
if it wasn't sent to lkml. That wasn't possible before bk. It's the
next best thing to actually having the author of the patch think others
may want the same patch Linus wants.
-- Skip - 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/