From owner-svn-src-stable@freebsd.org Thu Mar 15 16:20:31 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 34613F5E575 for ; Thu, 15 Mar 2018 16:20:31 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AFF0169634 for ; Thu, 15 Mar 2018 16:20:30 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: b3619877-286c-11e8-bb8e-b35b57339d60 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound1.ore.mailhop.org (Halon) with ESMTPSA id b3619877-286c-11e8-bb8e-b35b57339d60; Thu, 15 Mar 2018 16:19:57 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w2FGKRGP026047; Thu, 15 Mar 2018 10:20:27 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1521130827.99081.43.camel@freebsd.org> Subject: Re: svn commit: r330972 - stable/11/share/misc From: Ian Lepore To: rgrimes@freebsd.org Cc: Justin Hibbits , Andriy Gapon , Eitan Adler , src-committers , svn-src-all@freebsd.org, svn-src-stable@freebsd.org, svn-src-stable-11@freebsd.org Date: Thu, 15 Mar 2018 10:20:27 -0600 In-Reply-To: <201803151614.w2FGEttu093805@pdx.rh.CN85.dnsmgr.net> References: <201803151614.w2FGEttu093805@pdx.rh.CN85.dnsmgr.net> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit 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, 15 Mar 2018 16:20:31 -0000 On Thu, 2018-03-15 at 09:14 -0700, Rodney W. Grimes wrote: > > > > On Thu, 2018-03-15 at 10:52 -0500, Justin Hibbits wrote: > > > > > > On Thu, Mar 15, 2018 at 10:46 AM, Ian Lepore > > > wrote: > > > > > > > > > > > > I agree completely with all of this.??It bothers me how many > > > > committers > > > > have the attitude that handling MFCs is not part of being a > > > > committer. > > > Never attribute to arrogance that which can adequately be > > > explained > > > by > > > sheer laziness ;) > > > > > > - Justin (guilty of marking changes as MFC after, and ignoring > > > them > > > for far too long) > > > > > Laziness and procrastination I understand -- I own a lovely glass > > house > > in that neighborhood. ?I tend to put off MFCs for way too long then > > every few months have to spend a whole weekend catching up. > MFC: 1 week (by pool|self) #defaults to self if missing > > There is already a very nice tracking tool for outstanding MFC's, > if we added a bit of smarts in its parser, and created a pool of > MFC commiters (Eitan seems to have started one :-)) those who > do not want to do there own MFC work could pass the hat. If you're talking about the MFC after: field in commits, I don't use it. I have about zero tolerance for being nagged by anybody about anything, and that goes double for robots nagging me with spam mail. The MFC tool that works well for me is gonzo's MFCTracker site [*] that doesn't require extra markup in the commit messages. [*] https://mfc.kernelnomicon.org/6/ -- Ian