cvs commit: src/lib/libpthread Makefile src/lib/libpthread/test sigsuspend_d.c src/lib/libpthread/thread thr_cancel.c thr_concurrency.c thr_create.c thr_find_thread.c thr_init.c thr_kern.c thr_nanosleep.c thr_private.h thr_sig.c thr_sigmask.c...

David O'Brien obrien at
Fri Jul 18 18:56:09 PDT 2003

On Fri, Jul 18, 2003 at 05:45:46PM -0700, Marcel Moolenaar wrote:
> On Fri, Jul 18, 2003 at 05:15:24PM -0700, David O'Brien wrote:
> > 
> > Who are "the arches"?  KSE is a new feature, so the responsibility is on
> > the KSE developers to complete their implementation on all Tier-1
> > platforms.
> No. If there's not enough support from <arch>-gurus, then <arch>
> should be bumped down to tier 2.

In general I agree.

> We cannot realisticly require MI
> developers to know the MD details of all tier 1 platforms. We
> need to have active maintainers for the MD bits. If they don't
> exist, then we cannot really support the platform anyway.

HOWEVER, in this case, you can only take that line if you are paying for
the labor.  All our platforms have MD maintainers today -- but that does
not mean they are interested in doing KSE work.  KSE is the new comer,
not the existing Tier-1 platforms; thus the is the KSE developers that
need to have a complete implementation or not commit the work at all.

-- David  (obrien at

More information about the cvs-all mailing list