From owner-freebsd-current Sat Aug 22 16:00:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16096 for freebsd-current-outgoing; Sat, 22 Aug 1998 16:00:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from localhost.my.domain (ppp1606.on.bellglobal.com [206.172.249.70]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16067 for ; Sat, 22 Aug 1998 15:59:58 -0700 (PDT) (envelope-from hoek@FreeBSD.ORG) Received: from localhost (tim@localhost) by localhost.my.domain (8.8.8/8.8.8) with SMTP id SAA00994; Sat, 22 Aug 1998 18:58:37 -0400 (EDT) (envelope-from ac199@hwcn.org) X-Authentication-Warning: localhost.my.domain: tim owned process doing -bs Date: Sat, 22 Aug 1998 18:58:36 -0400 (EDT) From: Tim Vanderhoek X-Sender: tim@localhost Reply-To: ac199@hwcn.org To: Jonathan Lemon cc: Patrick Hartling , freebsd-current@FreeBSD.ORG Subject: Re: Not receiving CVS commit messages In-Reply-To: <19980822121417.21415@right.PCS> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 22 Aug 1998, Jonathan Lemon wrote: > I believe that the postmaster dropped all the cvs-* mailing > lists, except for cvs-all. The rationale was that almost Actually, I think it was wosch. He did so because jmb (the postmaster) had accidentally caused all commit messages cross-posted to several cvs-* lists to bounce. When jmb fixed this condition, no one bothered to re-enable the posting of commit messages to each relevant cvs-* list. At least, that's how I understand what happened. :-) Since it took this long to get even one complaint, I doubt anyone's going to re-enable this again, soon... -- This .sig is not innovative, witty, or profund. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message