From owner-svn-src-stable@freebsd.org Thu Mar 29 18:05:30 2018 Return-Path: Delivered-To: svn-src-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EAF35F68E73 for ; Thu, 29 Mar 2018 18:05:29 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x22c.google.com (mail-it0-x22c.google.com [IPv6:2607:f8b0:4001:c0b::22c]) (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 432087BE9B for ; Thu, 29 Mar 2018 18:05:29 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x22c.google.com with SMTP id c1-v6so8915311itj.1 for ; Thu, 29 Mar 2018 11:05:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=5dldukiHLxiGO8KXuhsLtOVSory8Rxs3olS5e3EmDuo=; b=bgleIBP33BiCaUwmiGHh/oDs9A4DU2etEwjJbVA5obE0bmUc6cNYDoskOpixUmJLcC FqIBB5THKRiRrDU+4HYOCrFXzqeK2UjfEwsLjE4L0gNH9p4TonAMereoFNYmysIuqADn ObKrv3YFsO2rhEnSBGi2JfDSjnp10BFbnPCUnojmE1HIwHctIaojOtnmE0aAUlLEe20g QzxmQEhZHOFLdyZnxx9ZKlb8JXwpPoRhmGYaMH5UL6izU7Ylm13JyzskUh7KsNjn8xTe 98K8ob7bWfihL+Jg0Y0bZ40OVcPhy76pO1tTDJPzV4IHdC+JfLdF0MHbVeGvT3UZJ9S7 hjsQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=5dldukiHLxiGO8KXuhsLtOVSory8Rxs3olS5e3EmDuo=; b=L8JYIgfumzYb+NNv06JDakXoaCfSmCEKJOl2HEnJTGQ7gyaQKHp5GGvsduAZUD+TQU gvbgBSvXXGvYR9CA3ycMMhmUt+VoJL78JMZimO2+yiwI6lfYpRpbNzEaIG35hM2Wj2lF I3s//yi0POWcOH9AJeHUDA8g+WsARlzo2KNzPRD3uRx65TzH3+jkbu3+XE2nvK474321 yC0vVCcxWeTnE2JmxDT9c7ZYjas5APg7lT7jF0KI81GhldDClIZn286QlWQfDMQ0yl3V SvVUvjeLbKW9EBJet706yiKKxSiPFqO9lVkVt/jnSL8IpF1XQLydykZIbRExh7X7QteZ oiGQ== X-Gm-Message-State: AElRT7HSBYxl8WI5f7FCZs/+sBb14dDc/G4PB9HeeqjncvXmTCKH+GO2 tntwW8d9u8rCCPh5CKVOamUxcPa5lHNpC+918qkirA== X-Google-Smtp-Source: AIpwx48BHxv0SvEXe2Ix5i2iD0+VJNAvMPzy713OJCdwt/VNvvtA6S9kRmo8YB5/UvKjO6OqPSvZByfPs9L+eNLf91A= X-Received: by 2002:a24:b649:: with SMTP id d9-v6mr8907096itj.51.1522346728629; Thu, 29 Mar 2018 11:05:28 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.203.196 with HTTP; Thu, 29 Mar 2018 11:05:27 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <1736582.AJYahrK36B@ralph.baldwin.cx> References: <201803291633.w2TGXinX064128@pdx.rh.CN85.dnsmgr.net> <1736582.AJYahrK36B@ralph.baldwin.cx> From: Warner Losh Date: Thu, 29 Mar 2018 12:05:27 -0600 X-Google-Sender-Auth: U78F6w8CsTwwHJLjsBttqpfZbWw Message-ID: Subject: Re: svn commit: r331728 - in stable/11/etc: . rc.d To: John Baldwin Cc: "Rodney W. Grimes" , Ian Lepore , Marcelo Araujo , src-committers , svn-src-all@freebsd.org, svn-src-stable@freebsd.org, svn-src-stable-11@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: svn-src-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: SVN commit messages for all the -stable branches of the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Mar 2018 18:05:30 -0000 On Thu, Mar 29, 2018 at 11:45 AM, John Baldwin wrote: > On Thursday, March 29, 2018 09:33:44 AM Rodney W. Grimes wrote: > > > On Thu, 2018-03-29 at 06:20 -0700, Rodney W. Grimes wrote: > > > That's not a blocker for committing; plenty of time elapsed to allow > > > anyone to reject the change. IMO, even a flat-out rejection isn't a > > > blocker to committing except for things like random or crypto code that > > > require formal approval (but I'd certainly think hard about committing > > > if people rejected the change, and put some effort into finding a > > > compromise first). > > > > It seems that the Phabricator review system is somewhat disfunctional > > in that actual review is only happening in some cases. Some people > > have even stated they flat out hate it. Others say that it is the > > way to go. > > Despite its limitations, we are in a far better shape with phab than we > were without it. > > > As araujo@ pointed out he was a "reviewer", but as I'll point out > > he didnt accept the review, which causes the landing state to be > > wrong, and is kinda implied that anyone commiting a phabricator > > change has reviewed it anyway. > > Eh, I treat the 'reviewed by' line in the commit log itself as the > authoritative list. For phab I think folks who use it understand > that only those who "accepted" it are the actual approvers (this is > true in LLVM as well). > > > The problem is that most people are not notified that a review > > of a change is even in process until the commit lands, this is > > not a functional communications system. > > > > Requring us all to go sign up like imp@ did to receive all > > submitted reviews, imho, is also a non functional situation. > > People are welcome to create herald rules to sign up for notifications > for specific parts of the tree. That is open even to non-committers to > do. I don't think that is all that onerous as it gives users the > control to decide which parts of the tree they want to monitor. The number of reviews isn't onerous. However, as jhb points out, I have lots of reviews that have people added automatically in stand, for man pages, parts of the networking stack, etc. It's really not that hard to do. Lots of people monitor what's going on. > > ?I usually also add a note such as '(timed out)' > > > after the url, but I've noticed that doing so ruins the automatic > > > closing of the review and requires you to manually abandon it instead. > > > > There isnt a way to close it as commited/fixed in rXXXXXX manually? > > If not that is yet another shortcoming of phabricator that should > > be looked at. > > You can close without abandoning. (I've done it a few times by just > using "Close Revision"). I do think this is something that didn't used > to work. I've also noticed that recently phab has grown a "Edit Related > Objects" > that seems to let you associate commits with a commit so that you can > fix a review to be tagged to the commit that closed it if it doesn't > auto-close (this seems to be a very recent change). Prior to that, > I've closed the revision with a comment using the right syntax > (rS) that turns into a hyperlink to the commit in the comment > closing the review (a bare SVN-style r won't do the hyperlink). > Now that's handy for when I misspell Differential Revision: or some other crazy thing happens so the revision isn't closed. Thanks for the useful tip. Warner