Date: Tue, 4 May 1999 15:25:53 -0700 (PWT) From: Matthew Jacob <mjacob@feral.com> To: Eivind Eklund <eivind@FreeBSD.org> Cc: Guy Helmer <ghelmer@scl.ameslab.gov>, "Kenneth D. Merry" <ken@plutotech.com>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.bin/mt mt.1 Message-ID: <Pine.LNX.4.04.9905041522070.14744-100000@feral.com> In-Reply-To: <19990504232121.C49159@bitbox.follo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Tue, May 04, 1999 at 12:11:36PM -0700, Matthew Jacob wrote: > > To follow up on this for the rest of CVS committers- What I see a lot of > > in FreeBSD commits is changes w/o checking with nominal last authors of > > code (and man pages are code). If it isn't that hard to do, can we please > > check with each other- even on trivial things- it's not *that* much extra > > email. > > The problem isn't the amount of e-mail you have to send out. The > problem is that a lot of people don't bother/remember to reply, which > means you have to keep track of a million changes (with PR numbers etc > if applicable) over a period of time, instead of being able to handle > the case at once. You can't even rely on e-mail on the subject coming > back as a way of finding out when to handle it. Send the email. Wait a reasonable period of time (fudge factor- 10 line change == 10 minute, 100 line change == 100 minutes, 1000 line change == overnight) and then make the change. The point here is to allow a nominal maintainer a look- if they're not paying attention, that's not your fault. Increasing useful communications is good. 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.LNX.4.04.9905041522070.14744-100000>