This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: [patch] remove Tix
- From: "Nick Kelsey" <nickk at ubicom dot com>
- To: "Andrew Cagney" <ac131313 at redhat dot com>
- Cc: <gdb at sources dot redhat dot com>
- Date: Thu, 28 Nov 2002 19:59:00 -0800
- Subject: Re: [patch] remove Tix
- References: <1038424481.1963.0.camel@Imp> <20021128032632.GB28564@redhat.com> <redirect-4640103@silicondust.com>
Hi Andrew,
> 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 have to admit that I usually use CVS through a GUI so I would need to look
up the procedure but deleting files works fine just as long as you get CVS
to do it and don't manually delete the files on the server.
Nick
> *This message was transferred with a trial version of CommuniGate(tm) Pro*
> > On Wed, Nov 27, 2002 at 11:14:40AM -0800, Martin M. Hunt wrote:
> >
> >>2002-11-27 Martin M. Hunt <hunt@redhat.com>
> >>
> >> * generic/gdbtk.c (gdbtk_init): Don't call Tix_Init.
> >> Don't include tix.h
> >>
> >> * generic/gdbtk-hooks.c: Don't include tix.h.
> >>
> >> * generic/gdbtkj-cmds.c: Don't include tix.h.
> >
> >
> > Does this mean that we can remove tix from the insight module
> > on sources dot redhat dot com?
>
> Not really.
>
> If tix was removed, someone checking out:
> -D last-year insight
> would find that the no longer got tix (which was needed back then).
>
> Might end up doing something like adding a module:
> insight-5-3
>
> Andrew
>
>
>