Date: Sun, 18 Apr 2004 12:13:10 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: sam@errno.com Cc: obrien@FreeBSD.org Subject: Re: cvs commit: src/gnu/usr.bin/binutils/libbfd/i386 bfd.h Message-ID: <20040418.121310.14063680.imp@bsdimp.com> In-Reply-To: <0B2DC895-9160-11D8-A7E1-000A95AD0668@errno.com> References: <20040418164651.GB62817@dragon.nuxi.com> <20040418170730.GB65020@dhcp01.pn.xcllnt.net> <0B2DC895-9160-11D8-A7E1-000A95AD0668@errno.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <0B2DC895-9160-11D8-A7E1-000A95AD0668@errno.com>
Sam Leffler <sam@errno.com> writes:
: On Apr 18, 2004, at 10:07 AM, Marcel Moolenaar wrote:
:
: > On Sun, Apr 18, 2004 at 09:46:51AM -0700, David O'Brien wrote:
: >>>
: >>> I have 6.1 pre-release in perforce. I plan to import that alongside
: >>> gdb 5.2 as soon as 6.1 is announced.
: >>
: >> What do mean "along side"? Please don't import src/contrib/gdb6.
: >
: > Yes, I'll import to gdb6
:
: I think having both gdb and gdb6 in CVS is a mistake. If it needs
: more testing do it outside the tree.
There's a limit to the amount of testing that can be done outside of
the tree. Or more accurately, there's a limit to the amount of
testing that happens outside of the tree. I thought my pci patches
were very close to being perfect, when in fact there were some big
holes that weren't discovered until after I committed it to the tree.
People rarely run things unless 'forced' to do so.
In the past, we've done this sort of import as a process to get things
going, and then deleted the files from CVS repo to not bloat it too
badly. After things were complete, the files were re-imported on top
of the traditional place.
I'm not sure that's the right thing to do in this case, but I thought
I'd mention some history here.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040418.121310.14063680.imp>