From owner-svn-ports-all@freebsd.org Mon Aug 6 00:30:57 2018 Return-Path: Delivered-To: svn-ports-all@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 7660F1063EA5; Mon, 6 Aug 2018 00:30:57 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: from mail-pg1-x544.google.com (mail-pg1-x544.google.com [IPv6:2607:f8b0:4864:20::544]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F36977F1AC; Mon, 6 Aug 2018 00:30:56 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: by mail-pg1-x544.google.com with SMTP id r5-v6so5397061pgv.0; Sun, 05 Aug 2018 17:30:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:reply-to:subject:to:cc:references:from:openpgp:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=kSHozP5drSKs14//bIdeVx5SrHP0lBqs3dhYmJKMxUo=; b=f/MSnCUIBVhiKkUqXU3mAMtYxye5MXJE44q6BGm8p7SVJCGht/FSuAxTEKvR+cu72G 0rFSCRvkv8dSBOoJ7OYYT8CfRge+y8M56wXZB8BPv/0sEMz93ED2lP+ZTByTPZRiM5Ip j4tOpmVDbydISRZK5WIfm6fpRbVL9vJAntjC8ay2vaRDac9f+VILUCO9W8th8dvdVQZZ mNOHFUEJFVJc58HBYmJBvj+XLbrDx44gmbV4VtRCQHFPVvZWBoMIg1zbkGJearGhEZxc bUVsfv4KnvPIcYdyNQapG01VQpPldTY5QNsHFKWVgL4KyrODbPLxlyoxwIHQ75Co/2JC 0zEg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:reply-to:subject:to:cc:references:from :openpgp:message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=kSHozP5drSKs14//bIdeVx5SrHP0lBqs3dhYmJKMxUo=; b=Wkit9+SFbOrLXkdYq55F26ZOgcCaPGWPvCA4p6zTcmbM57qayPrTFQgO6exPGfRO/i 6C2IZx950TuicEMUShxABIM7UFn0AzEUUDCErFN9udEFM5qys0w8r69h2AqvvZyDM6F3 y2jggtAnPfxZAWoqI+2C5lcj6XKYGwlyUJF2Xnv25K/3IO0gBhiwW2oki4g+zxE+ZoVZ F53e1IO1+mcurnJj1ynvBv2EFJc0ycSGH4BTI9u/tpEohh7WFe2HAQAZRaTkta9GP2Je q8x0XYOaRfwJvgPKL+6Ai6sOa0eiKIQU0MBB3GTMD7mvEup7QiANBW2CcXWzgzi1Fw7l UpcA== X-Gm-Message-State: AOUpUlHlmFKuJe+hUv+DvOqv3kgfEGGeyBjdIqqdjTZSTXDemXDWffH0 fyWeEPUDybqtdN91sePR0pV6znPh X-Google-Smtp-Source: AAOMgpcerv11jgWbUZDoPzM4N6jD3NtauTBQedajG1EexrmWI3wMKBNAAz/s1CVqBieNoC87HI+w0Q== X-Received: by 2002:a62:b29c:: with SMTP id z28-v6mr14874867pfl.8.1533515455616; Sun, 05 Aug 2018 17:30:55 -0700 (PDT) Received: from [192.168.1.107] ([103.107.240.136]) by smtp.gmail.com with ESMTPSA id q65-v6sm16993867pfj.127.2018.08.05.17.30.53 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 05 Aug 2018 17:30:55 -0700 (PDT) Sender: Kubilay Kocak Reply-To: koobs@FreeBSD.org Subject: Re: svn commit: r476475 - head/devel/include-what-you-use To: Adam Weinberger Cc: rene@freebsd.org, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org References: <201808052045.w75Kjlnl059608@repo.freebsd.org> From: Kubilay Kocak Openpgp: preference=signencrypt Message-ID: Date: Mon, 6 Aug 2018 10:30:50 +1000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Aug 2018 00:30:57 -0000 On 6/08/2018 10:04 am, Adam Weinberger wrote: > On Sun, Aug 5, 2018 at 5:32 PM Kubilay Kocak wrote: >> >> On 6/08/2018 6:45 am, Rene Ladan wrote: >>> Author: rene >>> Date: Sun Aug 5 20:45:47 2018 >>> New Revision: 476475 >>> URL: https://svnweb.freebsd.org/changeset/ports/476475 >>> >>> Log: >>> devel/include-what-you-use: update to version 0.10 >>> >>> This version uses clang 6.0 >>> >>> Take over maintainership. >>> >>> Approved by: koobs (implicit, three consecutive maintainer timeouts) >> >> While 'technically correct', there's plenty of evidence I'm active >> (particularly of late), and the timeouts referenced date back to 2016. >> >> 2016-12-27 215211 >> 2017-12-24 223537 >> 2018-01-31 224617 >> >> Please revert the maintainer change and in future for maintainer >> changes, submit a PR with a maintainer change patch, and let that >> timeout. That's explicit. > > The question of whether you're active in general is orthogonal to > whether you're actively maintaining a specific port, and is why we > support changing maintainership on a port-by-port basis. Perfectly understandable and never in question. > René's maintainer change was by-the-book, and it's not possible to > guarantee you a reset pattern different from what all other > maintainers get. 'Technically' correct as mentioned, yes. I've asked for a revert on the basis that the reset for a consecutive timeout period of over 2 years and in this case without any other change (or PR). In cases where I cannot make a change myself given a time constraint, my default workflow/policy is to approve the change (where QA'd) and unblock the submitter. There was no opportunity to do so in this case. I'm still asking for the change to be reverted.