From owner-freebsd-stable@FreeBSD.ORG Tue Jul 17 18:40:10 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 307F1106564A for ; Tue, 17 Jul 2012 18:40:10 +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 D6AFF8FC16 for ; Tue, 17 Jul 2012 18:40:09 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id q6HIe1d7078218; Tue, 17 Jul 2012 12:40:01 -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 q6HIe0QP078215; Tue, 17 Jul 2012 12:40:00 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Tue, 17 Jul 2012 12:40:00 -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 12:40:01 -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 18:40:10 -0000 On Tue, 17 Jul 2012, Eitan Adler wrote: > On 17 July 2012 10:10, Warren Block wrote: >>> 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? > > Some people find the PR ones annoying. ;) > A better answer: because sometimes I make a deliberate decision to > *not* MFC something even though it says "MFC after" Right now, there's no way for anyone but the original committer to tell whether an MFC has been forgotten, is delayed, no longer applies, or any other reason. >> 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? > > svn mergeinfo --show-revs eligible But those are just commits that svn sees as eligible for a merge, not ones with an actual "MFC after" message. > The OP seemed interested in writing a script to make this output usable. I'd be interested in this also.