Date: Mon, 8 Jun 1998 09:29:22 -0500 (CDT) From: Steve Price <sprice@hiwaay.net> To: Peter Hawkins <thepish@FreeBSD.ORG> Cc: Bruce Evans <bde@zeta.org.au>, cvs-committers@FreeBSD.ORG Subject: Re: cvs commit: src/sbin/mountd netgroup.5 Message-ID: <Pine.OSF.3.96.980608092025.24450B-100000@fly.HiWAAY.net> In-Reply-To: <Pine.BSF.3.96.980608210007.11826E-100000@dana.clari.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 8 Jun 1998, Peter Hawkins wrote: # Grin - exactly the opposite of what I was told last time by someone else # about overfilling logs. Is there a standard on procedure for committing # anywhere? Actually I was trying to say the same thing, but I may not have been clear enough. Here is an example of how I would tackle the Log: section of a commit related to a PR. in -current: Log: This is a long-winded commit message describing a change that I made which essentially changes foo to bar. PR: 10001 Submitted by: jim.smith@beer.org Revision 1.16 and in -stable: Log: MFC: foo -> bar or another approach would be: Log: MFC: revision 1.16 Does this clear things up? Steve # Peter # # Hilink Internet Peter Hawkins # 381 Swan St Richmond, # Vic, Australia Ph: +61-3-9421 2006 Fax: +61-3-9421 2007 # http://www.hilink.com.au Peter@hilink.com.au # # FreeBSD Project: thepish@FreeBSD.org # # To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.OSF.3.96.980608092025.24450B-100000>