From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Doug Evans <dje@google.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: [patch#2 3/6] set auto-load local-gdbinit warn-and-*
Date: Thu, 05 Apr 2012 16:53:00 -0000 [thread overview]
Message-ID: <20120405165307.GA9213@host2.jankratochvil.net> (raw)
In-Reply-To: <CADPb22TwB9tBASJU4D=widAHDZOfXc6UWXkfS0k3DbrMT+nKVQ@mail.gmail.com>
On Thu, 05 Apr 2012 18:27:51 +0200, Doug Evans wrote:
> "on" reads much better to me.
"on" sure reads OK but do you read OK "warn-and-on" and "warn-and-off"?
> > There are two possibilities:
> > Â * Introduce new option some "set local-gdbinit-warning <boolean>" as
> > Â suggested by Doug IIUC and technically keep everything boolean.
>
> For completeness sake,
> I was suggesting making the option more general, applying to more to
> more than just local-gdbinit (assuming more applications were readily
> available).
The warning is there duue to local-gdbinit (possible) deprecation. No other
file is being deprecated.
To apply it for example to use of deprecated GDB commands (and not files)
I somehow find too unrelated, I do not see any need / usefulness of such
warning.
Thanks,
Jan
next prev parent reply other threads:[~2012-04-05 16:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 9:13 Jan Kratochvil
2012-03-29 20:58 ` Doug Evans
2012-03-30 6:28 ` Eli Zaretskii
2012-03-30 6:33 ` Doug Evans
2012-03-30 6:45 ` Jan Kratochvil
2012-03-30 18:08 ` suspend: " Jan Kratochvil
2012-03-30 7:26 ` Eli Zaretskii
2012-04-02 20:31 ` [doc patch] objfile -> @var{objfile} [Re: [patch#2 3/6] set auto-load local-gdbinit warn-and-*] Jan Kratochvil
2012-04-02 21:10 ` Eli Zaretskii
2012-04-02 21:13 ` Jan Kratochvil
2012-04-02 21:19 ` Eli Zaretskii
2012-04-03 18:33 ` [patch#2 3/6] set auto-load local-gdbinit warn-and-* Jan Kratochvil
2012-04-05 16:15 ` Eli Zaretskii
2012-04-05 21:00 ` Jan Kratochvil
2012-04-05 16:28 ` Doug Evans
2012-04-05 16:53 ` Jan Kratochvil [this message]
2012-04-05 17:03 ` 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=20120405165307.GA9213@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=dje@google.com \
--cc=eliz@gnu.org \
--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