Re: Suggestion re: [PATCH] Remove Bitkeeper documentation from Linux tree

[Daniel Phillips <phillips@bonn-fries.net>]

On Sunday 21 April 2002 20:30, Jeff Garzik wrote:
> On Sat, Apr 20, 2002 at 08:23:49PM +0200, Daniel Phillips wrote:
> > At the moment I'm thinking about returning to the patchbot project (by the
> > way, code *is* available now) and reworking it to handle both BK and GNU
> > patches.  The advantage of the patchbot is, it can do things like sniff
> > patches for NOTIFYMEONCHANGE directives, auto-CC a linux-patches list,
> > etc.  It could act as an accumulator of GNU patches into a BK repository,
> > waiting for Linus to pull, and in the interim, all interested observers
> > could also peek into the repository.
> 
> Go for it.  If you build it, they will come...
> I'll reserve judgement until it is up and running, not just code available.
> There has been lots of talk about patchbots, but I haven't seen anyone
> crowing about their general-use patchbot on lkml.
> 
> I seriously doubt your system will work with GNU patches, though, as
> they still go privately to Linus.  A big advantage of this patchbot
> would be to expose GNU-style patches that would otherwise be "hidden" in
> various BK repostories until Linus does a pull and a pre-patch.
> 
> (encouraging people to CC all patches to the patchbot would be a good
> step, though, IMO)

In fact, the basic premise is that people mail to the patchbot, not the
maintainer.  The patchbot knows who the maintainer is and forwards the patch
to the maintainer, using the maintainer's format of choice, or as now
proposed, just drops it into the BK repository and forwards a notification,
both to the maintainer and the linux-patches list.

-- 
Daniel