From owner-cvs-all@FreeBSD.ORG  Sun Dec 26 18:41:42 2004
Return-Path: <owner-cvs-all@FreeBSD.ORG>
Delivered-To: cvs-all@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 680)
	id AE61B16A4CF; Sun, 26 Dec 2004 18:41:42 +0000 (GMT)
Date: Sun, 26 Dec 2004 18:41:42 +0000
From: Darren Reed <darrenr@hub.freebsd.org>
To: Sam Leffler <sam@errno.com>
Message-ID: <20041226184142.GB18879@hub.freebsd.org>
References: <200412250048.iBP0mSto090429@repoman.freebsd.org>
	<20041226083448.GA93350@hub.freebsd.org> <xzppt0x2px3.fsf@dwp.des.no>
	<20041226144953.GB93350@hub.freebsd.org> <41CF0326.9090704@errno.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <41CF0326.9090704@errno.com>
User-Agent: Mutt/1.4.2.1i
cc: Dag-Erling Sm?rgrav <des@des.no>
cc: src-committers@FreeBSD.org
cc: Scott Long <scottl@FreeBSD.org>
cc: cvs-all@FreeBSD.org
cc: cvs-src@FreeBSD.org
Subject: Re: cvs commit: src/sys/contrib/ipfilter/netinet ip_fil.h
X-BeenThere: cvs-all@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: CVS commit messages for the entire tree <cvs-all.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-all>,
	<mailto:cvs-all-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/cvs-all>
List-Post: <mailto:cvs-all@freebsd.org>
List-Help: <mailto:cvs-all-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-all>,
	<mailto:cvs-all-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Dec 2004 18:41:42 -0000

On Sun, Dec 26, 2004 at 10:29:58AM -0800, Sam Leffler wrote:
> >
> >>You seem to fail to do that with appalling regularity.
> >
> >
> >It's unfortunate that it happens but it does.
> >
> >I wish the solution was as easy as your implied suggestion but,
> >sorry, it isn't.
> 
> Have you considered finding another committer to take responsibility for 
>  this code?  If you can't run an up to date current system to validate 
> changes (not just compilation but also stability in operation) then it 
> sounds like there will continue to be problems.

I wish someone would step forward...I'm going to have significantly less
time (and opportunity, I think) in 2005 to do this than I have in 2004.

And I'd prefer it if someone did step forward...it's not hard keeping it
upto date, just mechanical and time consuming.

Darren