From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] Remove doc/libgdb.texinfo
Date: Wed, 23 Jan 2002 10:38:00 -0000 [thread overview]
Message-ID: <3C4F0302.90009@cygnus.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1020121114857.16755H-100000@is>
> On Sun, 20 Jan 2002, Andrew Cagney wrote:
>
>
>> The file libgdb.texinfo which dates back to '93 turns out to not be used
>> in current documentation. Adding to the fun, it is still (C) Cygnus
>> (oops!).
>>
>> I can think of two possible things to do to that file:
>>
>> o delete it (per attached)
>>
>> o make it FSF (Red Hat nee Cygnus have
>> no problems there) and say integrate
>> it into gdbint.texinfo as an historical
>> reference.
>>
>> thoughts?
>
>
> My vote is for removing that file altogether. It doesn't hold any
> useful information.
Ok, going, going, gone. trunk and 5.1 branch.
Andrew
prev parent reply other threads:[~2002-01-23 18:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-20 14:11 Andrew Cagney
2002-01-21 1:50 ` Eli Zaretskii
2002-01-23 10:38 ` Andrew Cagney [this message]
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=3C4F0302.90009@cygnus.com \
--to=ac131313@cygnus.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@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