From owner-freebsd-ipfw Wed Oct 2 7:22: 4 2002 Delivered-To: freebsd-ipfw@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D4BD537B401 for ; Wed, 2 Oct 2002 07:22:02 -0700 (PDT) Received: from mail.tcoip.com.br (erato.tco.net.br [200.220.254.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB16943E75 for ; Wed, 2 Oct 2002 07:22:00 -0700 (PDT) (envelope-from dcs@tcoip.com.br) Received: from tcoip.com.br ([10.0.2.6]) by mail.tcoip.com.br (8.11.6/8.11.6) with ESMTP id g92ELex16998; Wed, 2 Oct 2002 11:21:40 -0300 Message-ID: <3D9B00F3.9040308@tcoip.com.br> Date: Wed, 02 Oct 2002 11:21:39 -0300 From: "Daniel C. Sobral" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20020905 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Luigi Rizzo Cc: Danny.Carroll@mail.ing.nl, ipfw@FreeBSD.ORG Subject: Re: ipfw2 vs. ipfw1 and 4.7 References: <20021002064750.G22163@iguana.icir.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-ipfw@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Luigi Rizzo wrote: > in defense of daniel, this particular problem has a know fix (attached > to his message) and it "just" requires some amount of committer > time (more than what i have spent in replying to this thread) > to put it into stable, verify that it works as desired, get > re@ approval and do the commmit. > > Daniel is not a committer so the most he can do is remind me of the > pending MFC, which i appreciate. Now, the tone might have been > slightly different, but i am just looking at the good intentions > behind it. Actually, I am a committer. I don't know what I would have done or not had I suspected the fix had *not* been merged. I was, however, under the distinct impression it had already been merged. Looking back, I see that you said "which reminds me I have to...", so I got the impression you were going to do it, which somehow become the impression that you had done it. The fix was actually provided by yourself, in the message in which you asked for feedback given that 4.7 was entering the release process. I mentioned in my reply to that the bug *did* cause me trouble. Perhaps the trouble this caused me makes me touchy about it, but I extremely dislike known problems with known fixes left unattended on -stable, and I dislike this even more when we are preparing a release. Every bug in a release gives us a black eye. If we don't know about the bug, if it's difficult to reproduce, if the fix has subtle side-effects or has complications or is just plain difficult, I understand that. But a simple bug, easily reproduced, easily fixed, with no side effects? That does annoy me. > > cheers > luigi > > On Wed, Oct 02, 2002 at 03:38:20PM +0200, Danny.Carroll@mail.ing.nl wrote: > >>>From: Daniel C. Sobral [mailto:dcs@tcoip.com.br] >>>Sent: 01 October 2002 21:19 >>>I find it EXTREMELY inconvenient that 4.7 gets released with a KNOWN >>>bug, that was corrected in -current before we were halfway into the 4.7 >>>freeze. Even more so when the change does not affect *any* default >>>installation, because the feature must be explicitly enabled before this >>>code gets even installed. >> >>inconvenient? How about contributing? >>Most contributers are volunteers you know..... >> > -- Daniel C. Sobral (8-DCS) Gerencia de Operacoes Divisao de Comunicacao de Dados Coordenacao de Seguranca TCO Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: Daniel.Capo@tco.net.br Daniel.Sobral@tcoip.com.br dcs@tcoip.com.br Outros: dcs@newsguy.com dcs@freebsd.org capo@notorious.bsdconspiracy.net Preudhomme's Law of Window Cleaning: It's on the other side. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ipfw" in the body of the message