Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [PATCH 0/2] Use zuinteger_unlimited
Date: Fri, 15 Feb 2013 13:29:00 -0000	[thread overview]
Message-ID: <1360934868-5807-1-git-send-email-yao@codesourcery.com> (raw)

These two patches are to change commands to use zuinteger_unlimited,
as these commands are fit to zuinteger_unlimited command.

These two patches were original posted in this series as 2/3 and 3/3,

  [RFC 0/3] New var_types var_zuinteger_unlimited
  http://sourceware.org/ml/gdb-patches/2012-08/msg00020.html

during the review, I decided to post patch 1/3 together with other
changes here,

  [RFC 0/3] Get rid of var_integer in CLI
  http://sourceware.org/ml/gdb-patches/2012-08/msg00364.html

this series was approved by Tom and committed.  It is time to revisit the
patch 2/3 and 3/3 again.  I rebase them on the latest CVS trunk and
update changelog entry a little.

Regression tested on x86_64-linux.  Is it OK?

-- 
1.7.7.6


             reply	other threads:[~2013-02-15 13:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-15 13:29 Yao Qi [this message]
2013-02-15 13:29 ` [PATCH 1/2] use zuinteger_unlimited for some remote commands Yao Qi
2013-03-04 13:19   ` Pedro Alves
2013-03-04 14:38     ` Yao Qi
2013-03-04 16:21       ` Pedro Alves
2013-03-05  7:45         ` Yao Qi
2013-03-05 12:59           ` Pedro Alves
2013-03-05 17:33             ` Doug Evans
2013-03-05 18:07               ` Pedro Alves
2013-03-06  0:30                 ` Doug Evans
2013-02-15 13:29 ` [PATCH 2/2] use zuinteger_unlimited for heuristic-fence-post Yao Qi
2013-02-25  3:15 ` ping : [PATCH 0/2] Use zuinteger_unlimited Yao Qi

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=1360934868-5807-1-git-send-email-yao@codesourcery.com \
    --to=yao@codesourcery.com \
    --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