Date: Wed, 10 Jun 1998 13:38:46 +0800 From: Peter Wemm <peter@netplex.com.au> To: "Jordan K. Hubbard" <jkh@time.cdrom.com> Cc: Peter Hawkins <thepish@FreeBSD.ORG>, Bruce Evans <bde@zeta.org.au>, cvs-committers@FreeBSD.ORG Subject: Re: cvs commit: src/sbin/mountd netgroup.5 Message-ID: <199806100538.NAA04212@spinner.netplex.com.au> In-Reply-To: Your message of "Mon, 08 Jun 1998 04:21:36 MST." <21453.897304896@time.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Jordan K. Hubbard" 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? > > No, there's not, which is why you're getting such diametrically > opposed advice. :-) My advice is to just format them within reason and > make whatever citations you feel provide "sufficient info" since > there's no just way in creation that you're going to hit on a format > which pleases BOTH Bruce and the rest of us. It's not physically > possible. :-) A quick 1 or 2 liner would be best. Something like: MFC: rev 1.22-25: fix fubar in frobotz() routine PR: 9999 That way it's more obvious what it is. If you read the cvs log for the file and see the primary commits, it's a lot easier to figure out if it's already gone into 2.2.x or not with a quick cross-reference. Duplicating the entire log message is excessive, but enough to identify the source is good. The PR: on a seperate line seems to be something that some people use. > - Jordan > Cheers, -Peter -- Peter Wemm <peter@netplex.com.au> Netplex Consulting 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?199806100538.NAA04212>