Date: Mon, 9 Jan 2006 17:36:34 +0100 From: Tobias Roth <roth@iam.unibe.ch> To: Fernan Aguero <fernan@iib.unsam.edu.ar> Cc: ports@freebsd.org Subject: Re: New rc.d code merge timing (Was: Re: Portupgrade confused about editors/emacs) Message-ID: <20060109163634.GA26667@droopy.unibe.ch> In-Reply-To: <20060109141117.GC10941@iib.unsam.edu.ar> References: <20060106124508.GB14967@droopy.unibe.ch> <20060106125428.GC79296@pcwin002.win.tue.nl> <20060106131231.GC14967@droopy.unibe.ch> <43BF7430.80509@FreeBSD.org> <20060107191202.GA18881@droopy.unibe.ch> <43C0568F.7020909@rogers.com> <20060108001643.GA15000@soaustin.net> <43C05C21.4080500@rogers.com> <43C0B5E8.6030808@FreeBSD.org> <20060109141117.GC10941@iib.unsam.edu.ar>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 09, 2006 at 11:11:17AM -0300, Fernan Aguero wrote: > > Proposal: a ports-announce mailing list. This should be a > low-volume list where all HEADS UP of i) upcoming changes, > ii) committed changes are posted. Also, non-HEADS-UP > messages, like the ones that make up UPDATING should go to > the list. Messages could well be cross-posted to ports, so > that everyone gets the announcements. But I guess it could > be a good alternative for people that want just the > anouncements. If someones gets an announcement and wants to > see the discussion that lead to the changes, then s/he can > go to the ports@, stable@ and/or current@ archives. Excellent idea, I second it. Especially the UPDATING stuff is often missed, even by people who have time to read ports@ regularly. cheers, t.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060109163634.GA26667>