From owner-svn-src-releng@FreeBSD.ORG Thu Oct 9 19:36:43 2014 Return-Path: Delivered-To: svn-src-releng@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0718E686; Thu, 9 Oct 2014 19:36:43 +0000 (UTC) Received: from mail-pa0-x232.google.com (mail-pa0-x232.google.com [IPv6:2607:f8b0:400e:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AFACAEE3; Thu, 9 Oct 2014 19:36:42 +0000 (UTC) Received: by mail-pa0-f50.google.com with SMTP id kx10so309315pab.37 for ; Thu, 09 Oct 2014 12:36:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=jfTQDBkN5+rMe7/XFWH5A5lny2Lk/H9dG5FxzPrDr48=; b=kfGrihDyTaDAgJ2tmxEZJRr7MKtgdbmAl0cNcV3Gken4Fb8znCIswrTXrSXP2yF0XE zeh5CrWLm2TWInrOMXtwIdHu5K9spSLjl/+WoGpoc6d4+H27NlGI+jv2WxaoQetXp4a9 a1J0hXLG4rjRTN4NdCUpow/fbxEemwyedC2jpvm3gkHUCr0mZBk58mHErBYEYn3dHT/X q1qWibGJG1Cw1Wt4isvI7+hHPxwNA7PvHbgWF13xFgT/Mq23mNzRhiHUwSzy5IG5ng8L EXkT1WDm3G/hmZuQRy2y6l0bfwRkR7L1SGD/7QLvIHCMEn4cSSV5N0wZn5m0RApjaDiP c52w== X-Received: by 10.68.220.10 with SMTP id ps10mr76712pbc.135.1412883402128; Thu, 09 Oct 2014 12:36:42 -0700 (PDT) Received: from [10.61.9.12] (mobile-166-137-212-101.mycingular.net. [166.137.212.101]) by mx.google.com with ESMTPSA id nk11sm1291421pdb.40.2014.10.09.12.36.41 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 09 Oct 2014 12:36:41 -0700 (PDT) References: <201410081539.s98FdPQo052864@svn.freebsd.org> <2a6d01cfe37c$ef5cf410$ce16dc30$@FreeBSD.org> <2b3301cfe39b$f2ae29d0$d80a7d70$@FreeBSD.org> <2c4401cfe3e0$2abf3ff0$803dbfd0$@FreeBSD.org> Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: X-Mailer: iPhone Mail (11D257) From: Garrett Cooper Subject: Re: svn commit: r272752 - releng/10.1/sys/kern Date: Thu, 9 Oct 2014 12:36:37 -0700 To: Ed Maste Cc: "svn-src-releng@freebsd.org" , Neel Natu , "svn-src-all@freebsd.org" , "src-committers@freebsd.org" , Devin Teske , Neel Natu X-BeenThere: svn-src-releng@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: SVN commit messages for the release engineering / security commits to the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Oct 2014 19:36:43 -0000 > On Oct 9, 2014, at 11:32, Ed Maste wrote: >=20 >> On 9 October 2014 12:43, wrote: >>=20 >> I believe I have observed waxing and waning use of >> these acronyms, and your recent poll shows a current >> waning trend; however I wish more commits would: >>=20 >> a. describe the individual action in the message rather >> than the over-arching, higer-level action >> b. Use these acronyms more >=20 > I think it's silly to have to manually specify metadata in a commit > message which is already perfectly captured by the tool itself. The > manually-entered metadata is not 100% reliable across the projects > history anyway. >=20 > That said, I'd be happy to help review a proposed patch to the > committer's handbook or Subversion primer that documents these terms > and presents examples of their use. +1. Seems like a lot of drama over pedanticisms. Let me dig up the "MFC" script I have when I get home -- it automates the en= tire process. Thanks!=