Date: Thu, 02 May 2002 15:31:04 -0600 From: Warner Losh <imp@harmony.village.org> To: Mike Makonnen <makonnen@pacbell.net> Cc: Mike Silbersack <silby@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src UPDATING Message-ID: <200205022131.g42LV4r03480@harmony.village.org> In-Reply-To: Your message of "Thu, 02 May 2002 01:09:42 MDT." <1020323382.3871.37.camel@kokeb.ambesa.net> References: <1020323382.3871.37.camel@kokeb.ambesa.net> <200205020238.g422cIm56240@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <1020323382.3871.37.camel@kokeb.ambesa.net> Mike Makonnen writes: : On Wed, 2002-05-01 at 20:38, Mike Silbersack wrote: : > silby 2002/05/01 19:38:18 PDT : > : > Modified files: (Branch: RELENG_4) : > . UPDATING : > Log: : > Remove entry about ephemeral port range change MFC, as it : > has been un-MFC'd. : > : > Revision Changes Path : > 1.73.2.65 +0 -17 src/UPDATING : : Applogies if this has already been beaten to death. : : It seems to me that when changes like this one (where a previously made : change is un-done) are required in UPDATING, it would be better to add : another entry stating that the change has been un-done, instead of : removing it completely from UPDATING. Simply removing the relevant entry : can potentially be confusing to users who _do_ read UPDATING. My : reasoning is as follows: if the original change was important enough to : warrant a mention, then its reversal must also be just as important. That's how I've historically managed the file. It is a ticker that tells people what they need to know. Warner 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?200205022131.g42LV4r03480>