This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: [patch] remove Tix
- From: Christopher Faylor <cgf at redhat dot com>
- To: gdb at sources dot redhat dot com
- Date: Thu, 28 Nov 2002 23:38:35 -0500
- Subject: Re: [patch] remove Tix
- References: <1038424481.1963.0.camel@Imp> <20021128032632.GB28564@redhat.com> <redirect-4640103@silicondust.com> <006001c2975b$a6fdbc60$0a00a8c0@nkelseyhome>
On Thu, Nov 28, 2002 at 07:59:00PM -0800, Nick Kelsey wrote:
>>If tix was removed, someone checking out: -D last-year insight would
>>find that the no longer got tix (which was needed back then).
>
>I am all for removing redundant code.
>
>If tix isn't needed then marking it as deleted in CVS shouldn't affect
>someone checking out an earlier version - they would still get tix as
>long as it was before the delete date.
I was talking about removing tix from the gdb module, not "cvs
remove"ing it (although that's an option, too). Removing it from the
module will have the effect that Andrew describes since this just
involves editing the modules file in CVSROOT. Personally, I don't think
it is a big deal.
You either confuse every future person who wonders why they're getting
the tix directory when they don't need it or you insure that those rare
individuals who 'cvs checkout' past versions of insight will not be
bothered by the lack of tix.
Hmm. Sounds like tix can be removed from the top level Makefiles, too.
cgf