From: Tom Tromey <tromey@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [2nd try, RFC 0/2] Fix 'set remote XXX-limit -1' and 'set listisize'
Date: Fri, 14 Sep 2012 18:55:00 -0000 [thread overview]
Message-ID: <87vcfgzb7y.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1347160965-24089-1-git-send-email-yao@codesourcery.com> (Yao Qi's message of "Sun, 9 Sep 2012 11:22:43 +0800")
>>>>> "Yao" == Yao Qi <yao@codesourcery.com> writes:
Yao> I feel that people are not convinced to add a new var_type
Yao> var_zuinteger_unlimited, so I decide to fix the problem in another way
Yao> (don't add new var_type).
I thought it was fine; I think everybody is just very behind on patch
review. But if you'd still rather go with this approach, let me know,
and I'll look.
Tom
prev parent reply other threads:[~2012-09-14 18:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-09 3:23 Yao Qi
2012-09-09 3:23 ` [PATCH 1/2] Check the range Yao Qi
2012-09-09 3:24 ` [PATCH 2/2] Update doc and test of 'set listsize' Yao Qi
2012-09-09 17:27 ` Eli Zaretskii
2012-09-14 18:55 ` Tom Tromey [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=87vcfgzb7y.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.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