From owner-cvs-all Mon Jul 26 9:54: 0 1999 Delivered-To: cvs-all@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 2EC3514CB6; Mon, 26 Jul 1999 09:53:51 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id MAA03365; Mon, 26 Jul 1999 12:51:00 -0400 (EDT) Date: Mon, 26 Jul 1999 12:50:58 -0400 (EDT) From: Alfred Perlstein To: Dag-Erling Smorgrav Cc: Brian Somers , cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/net if_tun.c In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk On 26 Jul 1999, Dag-Erling Smorgrav wrote: > Alfred Perlstein writes: > > On Mon, 26 Jul 1999, Brian Somers wrote: > > > brian 1999/07/26 05:11:11 PDT > > > Log: > > > Don't complain if 0 bytes are written to the tun device, simply > > > do nothing. > > can you MFC this, there's no point in having current's and > > stable's API differ? > > Can you guarantee that it doesn't break anything? Before my patch it would panic both -current and -stable. > (BTW, this is semantics, not API, and I can think of a zillion other > ways in which the semantics of -CURRENT differ from those of -STABLE) yes, but my patch went in two days ago, and the API was changed just now. I still think it's an error to write a zero length packet to the tun device, but the API should be consistant. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message