lkml.org 
[lkml]   [2002]   [Apr]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Suggestion re: [PATCH] Remove Bitkeeper documentation from Linux tree
Date
On Tuesday 23 April 2002 08:04, Jamie Lokier wrote:
> Daniel Phillips wrote:
> > 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.
>
> Oh, now that _is_ a good idea. So individuals like me can register and
> say "notify me if anyone posts something for net/packet/* or
> include/linux/if_packet.h". Whether I'm a maintainer or not?

Yes, see the NOTIFYONCHANGE remark earlier. Some form of metadata in the file
could could be used to effect that, or the patchbot's database could record it.

Want to help throw code at this? I see the scope of this expanding.

> That would be pretty useful.
>
> An uber-feature would be "notify me if the VFS interface or locking
> rules change", for version 2 perhaps ;-)

Challenging, but doable. It's a database + command interface problem, and of
course, coding resource problem. Did you have a framework in mind?

--
Daniel
-
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.123 / U:0.644 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site