From: Christopher Faylor <cgf@redhat.com>
To: gdb@sources.redhat.com
Subject: Re: [patch] remove Tix
Date: Thu, 28 Nov 2002 20:38:00 -0000 [thread overview]
Message-ID: <20021129043835.GA17157@redhat.com> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2002-11-29 4:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1038424481.1963.0.camel@Imp>
[not found] ` <20021128032632.GB28564@redhat.com>
[not found] ` <redirect-4640103@silicondust.com>
2002-11-28 19:59 ` Nick Kelsey
2002-11-28 20:38 ` Christopher Faylor [this message]
2002-11-29 7:04 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021129043835.GA17157@redhat.com \
--to=cgf@redhat.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox