From owner-freebsd-ports@FreeBSD.ORG Mon Jan 9 14:11:51 2006 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 94B6316A41F; Mon, 9 Jan 2006 14:11:51 +0000 (GMT) (envelope-from fernan@iib.unsam.edu.ar) Received: from smtp.unsam.edu.ar (smtp.unsam.edu.ar [170.210.48.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id B7EC943D46; Mon, 9 Jan 2006 14:11:44 +0000 (GMT) (envelope-from fernan@iib.unsam.edu.ar) Received: from pi.iib.unsam.edu.ar (pi.iib.unsam.edu.ar [192.168.10.11]) by smtp.unsam.edu.ar (8.12.6/8.12.6) with ESMTP id k09EBAFZ028567; Mon, 9 Jan 2006 11:11:10 -0300 (ART) (envelope-from fernan@iib.unsam.edu.ar) Received: from pi.iib.unsam.edu.ar (localhost [127.0.0.1]) by pi.iib.unsam.edu.ar (8.13.1/8.13.1) with ESMTP id k09EBMLH094646; Mon, 9 Jan 2006 11:11:23 -0300 (ART) (envelope-from fernan@iib.unsam.edu.ar) Received: (from fernan@localhost) by pi.iib.unsam.edu.ar (8.13.1/8.13.1/Submit) id k09EBHwE094645; Mon, 9 Jan 2006 11:11:17 -0300 (ART) (envelope-from fernan@iib.unsam.edu.ar) X-Authentication-Warning: pi.iib.unsam.edu.ar: fernan set sender to fernan@iib.unsam.edu.ar using -f Date: Mon, 9 Jan 2006 11:11:17 -0300 From: Fernan Aguero To: Doug Barton Message-ID: <20060109141117.GC10941@iib.unsam.edu.ar> Mail-Followup-To: Doug Barton , Mike Jakubik , ports@freebsd.org, Mark Linimon References: <43BE63E7.4060209@rogers.com> <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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43C0B5E8.6030808@FreeBSD.org> User-Agent: Mutt/1.5.9i Cc: ports@freebsd.org, Mike Jakubik , Mark Linimon Subject: Re: New rc.d code merge timing (Was: Re: Portupgrade confused about editors/emacs) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jan 2006 14:11:51 -0000 +----[ Doug Barton (08.Jan.2006 03:51): | | Mike Jakubik wrote: | | >I was just curious, didn't mean to imply anything because i didn't | >notice anything on the lists about this. | | Well, I think we've reached a good place here with a civil exchange of | opinion. I feel compelled to point out that I sent several messages, to | -stable, -current, and -ports, before the code went into HEAD, after it | went into HEAD, and before and after it went into RELENG_6. I also sent | other HEADS UP messages to -ports about issues like cleaning up your | */etc/rc.d/ directories. | | Now I know that it's easy to miss things on the FreeBSD lists, but it's not | like this one was snuck in. :) OK, so, when you have time to go over the messages from the list, there's no problem. However, when you're busy with other things (most of the time for me. I'm not a sysadmin) filtering the announcements and HEADS UP from the rest of the chat can be too much ... I've been unsubscribed from ports for some time, since I had no spare time, this meant that to be safe (ie not break anything) I left my boxes without updates for a long time ... the list of my installed ports with entries in UPDATING was too long for my available time. 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. Of course there's also freebsd-announce@ but this seems more for security advisories and new release announcements ... we wouldn't want to pollute that list or do we? Sounds reasonable? Fernan | | > I fully understand the concept | >of having to take a step back to take two forward, i have the same | >situation with my career now. So thanks to both of you for putting in | >the time, hopefully we can weed out all the problems before 6.1. | | Agreed. | | | Doug | | -- | | This .signature sanitized for your protection | | _______________________________________________ | freebsd-ports@freebsd.org mailing list | http://lists.freebsd.org/mailman/listinfo/freebsd-ports | To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" | | +----]