From owner-svn-src-all@FreeBSD.ORG Mon Feb 16 22:24:48 2015 Return-Path: Delivered-To: svn-src-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F3E40AAD; Mon, 16 Feb 2015 22:24:47 +0000 (UTC) Received: from mail-lb0-f176.google.com (mail-lb0-f176.google.com [209.85.217.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 70757B5A; Mon, 16 Feb 2015 22:24:47 +0000 (UTC) Received: by lbiw7 with SMTP id w7so1176042lbi.9; Mon, 16 Feb 2015 14:24:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=96WE9SGbjWCd7tt5qAOyiNbSRqQLx6VIhnWte+ovXKw=; b=gMnoUlkQHtcla/NJU+grdehE9RC2O4F3z9ZcgzuaMFeMD1uWPL8z8IW6p3Dn3BShzZ mDyeKeXbx26ExTftUKvASCkpGGG0x9g2+2bphM5EA/4GVytI/5P/JU350iEukQ2KQmjQ 6hAtWJYD0rclgN7q/Vlbd6jdWGmK/3NomZciL9ubBspALWG3Inji3Efi2vABX+7/T9YF RV/1peM11Ky4vgeG6JX2bifa3YVbwtlkZZObED87zYUzkdmsTJNucNLcDdPpfZlfn4f1 XhDI84KS/llTFf95g6X+qS6N+Mu9JG3Qksw+TfSSOELc/jtv3Mu36UYxc0PbofawK851 AXEA== MIME-Version: 1.0 X-Received: by 10.112.181.165 with SMTP id dx5mr25555054lbc.89.1424125484478; Mon, 16 Feb 2015 14:24:44 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.112.28.40 with HTTP; Mon, 16 Feb 2015 14:24:44 -0800 (PST) In-Reply-To: <54E1B14E.10707@gmx.com> References: <201501060903.t06934qp081875@svn.freebsd.org> <20150122012709.GM15484@FreeBSD.org> <54C16715.6060701@gmx.com> <20150122222314.GO15484@FreeBSD.org> <20150215190100.GQ15484@FreeBSD.org> <20150216012528.GA15484@FreeBSD.org> <20150216074656.GE15484@FreeBSD.org> <54E1B14E.10707@gmx.com> Date: Mon, 16 Feb 2015 14:24:44 -0800 X-Google-Sender-Auth: r6wujh5HMuiLR3Ptig9qZbWHVno Message-ID: Subject: Re: svn commit: r276747 - head/sys/netpfil/pf From: Craig Rodrigues To: Nikos Vassiliadis Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "svn-src-head@freebsd.org" , "svn-src-all@freebsd.org" , Gleb Smirnoff , "src-committers@freebsd.org" X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2015 22:24:48 -0000 Cool. Having the PF + VIMAGE issues resolved and committed to HEAD is what I am most interested in. When you have a patch that you are happy with, would you be OK with getting it into Phabricator? It would be good to have it in there, so that multiple people can review it, including Gleb. Unfortunately, currently only committers can open reviews in Phabricator, so we would need to get your patch to a committer to enter in Phabricator. I can help with that, or you can hand off to another committer if you are more comfortable with that. Thanks! -- Craig On Mon, Feb 16, 2015 at 12:58 AM, Nikos Vassiliadis wrote: > Hi Gleb & Craig, > > I am already working on the issues that need to be fixed, namely: > 1) all the changes from projects/pf > 2) unloading the module > 3) one purge thread per pf instance will remain until we have > more experience > > It's almost ready, I am trying to fix unloading the module. > > As I am not at home this week I will send you a patch for review on > Monday. > > Best regards, > Nikos > > > On 02/16/15 09:02, Craig Rodrigues wrote: > >> On Sun, Feb 15, 2015 at 11:46 PM, Gleb Smirnoff >> wrote: >> >> On Sun, Feb 15, 2015 at 11:36:17PM -0800, Craig Rodrigues wrote: >>> C> On Sun, Feb 15, 2015 at 5:25 PM, Gleb Smirnoff >>> wrote: >>> C> >>> C> > On Sun, Feb 15, 2015 at 01:33:19PM -0800, Craig Rodrigues wrote: >>> C> > C> By the way, it would be helpful if you could provide feedback in >>> C> > C> Phabricator. When I created those Phabricator reviews, I added >>> C> > C> you as a reviewer to all of them, so you can't say that you >>> didn't >>> see >>> C> > C> the patches. >>> C> > C> You did not provide feedback on any of them: >>> C> > C> >>> C> > C> https://reviews.freebsd.org/D1309 >>> C> > C> https://reviews.freebsd.org/D1312 >>> C> > C> https://reviews.freebsd.org/D1313 >>> C> > C> https://reviews.freebsd.org/D1315 >>> C> > C> >>> C> > C> Please take some time to go and provide feedback in those >>> C> > C> reviews, so that a better patch can be made that makes you happy. >>> C> > >>> C> > Did you address all problems that arised after code was committed? >>> C> > >>> C> > Please do, otherwise my review would require me to cut-n-paste from >>> C> > my own emails. >>> C> > >>> C> >>> C> Yes, please cut and paste from your e-mails, and put in the reviews. >>> >>> No, I will not do this. You know right now that you have problems >>> in the aforementioned phab URLs, and you are asking me to look at >>> patches at to point them out to you. This is your task, not mine. >>> >>> Please address all already known problems and update the phab revisions. >>> >>> C> It's easier to follow in the individual reviews because there are >>> different >>> C> changes >>> C> in each review, rather than one big revert, which is what you did. >>> >>> I'm already starting to repeat myself. I did a big revert, because >>> the first change wasn't compilable, later changes fixed compilation >>> failures, but introduced unacceptable bugs. That's why I was forced >>> to back out all chain. >>> >>> >> >> >> It's not clear to me what parts you find unacceptable, >> and what parts you find acceptable. I added you to the reviews >> in Phabricator from the beginning, so it would have been nice if you could >> have >> provided the review feedback there. Since you are slow to provide >> feedback when I asked you to be a reviewer in Phabricator, but you >> are quick to revert changes, and provide unclear feedback during your >> reversion, >> this makes it very hard to make forward progress in this area. >> >> In the past, multiple like Nikos and Martin Matuska have been providing >> patches in your >> projects/pf branch, but you don't seem to have the time/interest to push >> these patches back into head. >> I've seen that Martin Matuska stopped waiting for you to merge the pf >> branch to head, and started cherry >> >> -- >> Craig >> >>