From: "Eli Zaretskii" <eliz@gnu.org>
To: Michael Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfc/testsuite/doco] deprecate.txt
Date: Fri, 10 Sep 2004 16:16:00 -0000 [thread overview]
Message-ID: <01c49751$Blat.v2.2.2$85ca7680@zahav.net.il> (raw)
In-Reply-To: <4141B12A.nail2461S2ZKE@mindspring.com> (message from Michael Chastain on Fri, 10 Sep 2004 09:50:34 -0400)
> Date: Fri, 10 Sep 2004 09:50:34 -0400
> From: Michael Chastain <mec.gnu@mindspring.com>
>
> Here is a new file, gdb/testsuite/deprecate.txt.
>
> I think it's more useful to keep this file inside gdb/testsuite rather
> than making it a section of doc/gdbint.texinfo . Eli, is that okay with
> you?
I won't fight you if you feel strongly about that, but let me ask:
why do you think it is better to keep this file separate? My
experience tells me that having several separate files is worse than
having a single file.
next prev parent reply other threads:[~2004-09-10 16:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-10 13:50 Michael Chastain
2004-09-10 16:16 ` Eli Zaretskii [this message]
2004-09-10 16:28 ` Michael Chastain
2004-09-10 19:28 ` Eli Zaretskii
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='01c49751$Blat.v2.2.2$85ca7680@zahav.net.il' \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.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