lkml.org 
[lkml]   [2002]   [Apr]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Suggestion re: [PATCH] Remove Bitkeeper documentation from Linux tree
> That's what I meant. Email gets sent out to LKML when the patch gets sent
> to BK for approval by Linus. Another email can then be sent out (unless
> it's felt that it's too verbose to do so) when Linus accepts it into the
> tree. (unless I'm missing something about BK ;)

OK, I think you are missing some details of the workflow used to get patches
to Linus. As far as I know, he mostly pulls rather than accepts patches,
that's one of the reasons there are so many different kernel repositories
on bkbits.net. They are mostly queues of stuff waiting for Linus to pull
them.

If that is correct, then what we really want is email when something
lands on bkbits.net and is not yet included in Linus' tree. We can
certainly set up a trigger to send email in that case.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
-
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/

\
 
 \ /
  Last update: 2005-03-22 13:25    [W:0.162 / U:1.508 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site