From owner-freebsd-current Fri Jan 31 19: 8:31 2003 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 931) id 4493337B401; Fri, 31 Jan 2003 19:08:30 -0800 (PST) Date: Fri, 31 Jan 2003 19:08:30 -0800 From: Juli Mallett To: Mike Barcroft Cc: Mark Linimon , freebsd-current@FreeBSD.ORG Subject: Re: State of the Union Report (backout request department) Message-ID: <20030131190830.B96430@FreeBSD.org> References: <200301311926.12431.linimon@lonesome.com> <20030131214318.E69408@espresso.q9media.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030131214318.E69408@espresso.q9media.com>; from mike@FreeBSD.org on Fri, Jan 31, 2003 at 09:43:18PM -0500 Organisation: The FreeBSD Project X-Alternate-Addresses: , , , , X-Towel: Yes X-LiveJournal: flata, jmallett X-Negacore: Yes Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * De: Mike Barcroft [ Data: 2003-01-31 ] [ Subjecte: Re: State of the Union Report (backout request department) ] > The archives might not be telling the whole story. A lot of times > these things get handled behind closed doors, whether private e-mail > or developer-only lists. Thankfully though, most conflicts *do* get > resolved. :) Might be nice if we had an internal trouble ticket system for things like this, TODOs that are high priority, and pending MFCs. I got the impression NetBSD does something like this for branch pullups that are needed? Then there's a clearer qudit trail, and it's easier to find out if things have "not been honoured". And to keep other sorts of things from falling behind. Thanx, juli. -- Juli Mallett AIM: BSDFlata -- IRC: juli on EFnet OpenDarwin, Mono, FreeBSD Developer ircd-hybrid Developer, EFnet addict FreeBSD on MIPS-Anything on FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message