From owner-freebsd-stable@FreeBSD.ORG Tue Jul 17 17:10:46 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 096961065673 for ; Tue, 17 Jul 2012 17:10:46 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id B285D8FC0C for ; Tue, 17 Jul 2012 17:10:45 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id q6HHAcXi077986; Tue, 17 Jul 2012 11:10:38 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id q6HHAbTA077983; Tue, 17 Jul 2012 11:10:37 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Tue, 17 Jul 2012 11:10:37 -0600 (MDT) From: Warren Block To: Eitan Adler In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Tue, 17 Jul 2012 11:10:38 -0600 (MDT) Cc: freebsd-stable@freebsd.org, David Magda Subject: Re: The MFC process... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jul 2012 17:10:46 -0000 On Tue, 17 Jul 2012, Eitan Adler wrote: > On 17 July 2012 09:53, Warren Block wrote: > >> I don't expect it to happen. But right now, there's only the initial mail >> that the MFC is due, and no reminder afterwards. We have the open PR mails >> once-weekly; MFCs are at least as important. > > I have a special place in my email for MFC reminder emails which I use > as a "todo" list. Getting weekly reminders would just be annoying. Why would it be a problem with with MFCs if it isn't a problem for PRs? >> Come to think of it, entering PRs for past-due MFCs could be a way to do >> that with the existing systems. > > We have this already: PRs in the 'patched' state. Unless there was no PR. Which brings up the question of how can we query for MFCs now? For example, how many MFCs are past due? What is the oldest one?