From: Stan Shebs <stanshebs@earthlink.net>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] Delete struct inferior_suspend_state
Date: Fri, 08 Aug 2014 23:25:00 -0000 [thread overview]
Message-ID: <53E55C6F.80901@earthlink.net> (raw)
In-Reply-To: <yjt2silh73aa.fsf@ruffy.mtv.corp.google.com>
On 7/31/14, 12:10 PM, Doug Evans wrote:
> Hi.
>
> I happened across some #if 0's in the code and thought that odd.
>
> I found the relevant thread here:
>
> https://sourceware.org/ml/gdb-patches/2012-06/msg00370.html
>
> Any desire to continue to keep this, or can we delete it?
> [I don't have a strong preference, but it feels like it's time.]
I was sure we had set a policy to delete code instead of doing #if 0,
but I can't find anything in writing that says so.
In any case, retaining dead code seems pointless when version control
systems make it easy to find again.
Stan
stan@codesourcery.com
next prev parent reply other threads:[~2014-08-08 23:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 19:30 Doug Evans
2014-07-31 19:46 ` Jan Kratochvil
2014-07-31 19:54 ` Doug Evans
2014-07-31 20:33 ` Joel Brobecker
2014-07-31 20:42 ` Doug Evans
2014-07-31 20:58 ` Joel Brobecker
2014-07-31 21:11 ` Doug Evans
2014-07-31 21:53 ` Joel Brobecker
2014-08-01 2:04 ` Doug Evans
2014-08-08 23:25 ` Stan Shebs [this message]
2014-08-09 20:53 ` Doug Evans
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=53E55C6F.80901@earthlink.net \
--to=stanshebs@earthlink.net \
--cc=gdb-patches@sourceware.org \
/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