On 20 Apr 2002, Andi Kleen wrote:
> > I don't buy that - I'm not getting changes from any new magical BK "men in
> > black". The patches are the same kind they always were, the last few
> > entries in my changelog are now the x86-64 merge (which was half a meg,
> > and yes it wasn't posted on linux-kernel, but no, it never was before BK
> > either), and before that the extensively discussed SSE register content
> > leak patch.
>
> I didn't post the huge patch on l-k because the last time I sent large
> patches to l-k I got flamed badly by people who still seem to use 9600
> baud modems[1] to read mail.
Note: I did in no way try to blame Andi on this: quite the reverse. I'm
saying that this was how it worked back before BK too - the bulk of the
patches literally come to me as "private" patches, and they aren't cc'd to
linux-kernel.
(Side note: that doesn't mean that they haven't had comments on the
mailing lists, or that earlier versions or at least parts of them haven't
been sent on the kernel list).
> I don't want to use BitKeeper because I don't like open logging. I hope
> I can continue to maintain the x86-64 port even without being part
> of the inner bitkeeper circle.
Absolutely - as you noticed I accepted the patch, even though there was a
clash (with a released kernel) in there.
> It would be good if you did e.g.
> a pre patch for every change that could require action from architecture
> or other maintainers as sync point (i guess that could be made easy with
> the appropiate script)
This is why I think it might be a good reason to just have a daily script:
not just to create the patches, but also to kind of keep a running
commentary on the kernel list on what I've merged..
Linus
-
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/
This archive was generated by hypermail 2b29 : Tue Apr 23 2002 - 22:00:27 EST