From: Pedro Alves <palves@redhat.com>
To: Patrick Palka <patrick@parcs.ath.cx>, Eli Zaretskii <eliz@gnu.org>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/2] Read $GDBHISTSIZE instead of $HISTSIZE
Date: Mon, 15 Jun 2015 14:54:00 -0000 [thread overview]
Message-ID: <557EE72D.10503@redhat.com> (raw)
In-Reply-To: <CA+C-WL9inyXvZtJWQFwFa-0hkCCZPQGzMiJGABbAB=v9pMEK6A@mail.gmail.com>
On 06/04/2015 04:30 PM, Patrick Palka wrote:
> Hmm, reading HISTSIZE as a last resort would reduce the inter-version
> breakage a little, at least for users who today rely solely on
> HISTSIZE (not ~/.gdbinit) to set their history size. This can be
> done, I guess.
I'd propose going ahead with the patch that ignores HISTSIZE and
seeing if anyone notices/complains.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-06-15 14:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 11:24 Patrick Palka
2015-05-22 11:24 ` [PATCH 2/2] Tweak the handling of $GDBHISTSIZE edge cases [PR gdb/16999] Patrick Palka
2015-05-22 11:57 ` Patrick Palka
2015-05-29 9:32 ` Pedro Alves
2015-06-17 19:18 ` Patrick Palka
2015-06-23 12:56 ` Yao Qi
2015-06-23 14:28 ` Patrick Palka
2015-05-22 12:30 ` [PATCH 1/2] Read $GDBHISTSIZE instead of $HISTSIZE Eli Zaretskii
2015-06-04 15:30 ` Patrick Palka
2015-06-15 14:54 ` Pedro Alves [this message]
2015-05-29 11:05 ` Pedro Alves
2015-06-17 18:19 ` Patrick Palka
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=557EE72D.10503@redhat.com \
--to=palves@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=patrick@parcs.ath.cx \
/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