From owner-cvs-all Mon Jun 8 07:29:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22229 for cvs-all-outgoing; Mon, 8 Jun 1998 07:29:32 -0700 (PDT) (envelope-from owner-cvs-all@FreeBSD.ORG) Received: from fly.HiWAAY.net (sprice@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA22218; Mon, 8 Jun 1998 07:29:24 -0700 (PDT) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by fly.HiWAAY.net (8.8.8/8.8.6) with SMTP id JAA03904; Mon, 8 Jun 1998 09:29:22 -0500 (CDT) Date: Mon, 8 Jun 1998 09:29:22 -0500 (CDT) From: Steve Price To: Peter Hawkins cc: Bruce Evans , cvs-committers@FreeBSD.ORG Subject: Re: cvs commit: src/sbin/mountd netgroup.5 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk 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