public inbox for
help / color / mirror / Atom feed
Subject: gdb and binutils branch master updated. b5be8ce022f894831b133b3b424238d8058eb29e
Date: Thu, 14 Nov 2013 10:32:00 -0000	[thread overview]
Message-ID: <> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gdb and binutils".

The branch, master has been updated
       via  b5be8ce022f894831b133b3b424238d8058eb29e (commit)
      from  671afef641d8cf0672e36d7afeb053c8d01c294e (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------;h=b5be8ce022f894831b133b3b424238d8058eb29e

commit b5be8ce022f894831b133b3b424238d8058eb29e
Author: Joel Brobecker <>
Date:   Mon Nov 11 09:19:32 2013 +0400

    New function cli-utils.c:extract_arg_const
    This function provides the exact same functionality as extract_arg,
    except that it takes a "const char**" instead of a "char **".
    It allows us also to re-implement extract_arg almost as a simple
    wrapper around the new function.
            Pedro Alves  <>
            Joel Brobecker  <>
            * cli/cli-utils.h (extract_arg_const): Add declaration.
            * cli/cli-utils.c (extract_arg_const): New function.
            (extract_arg): Reimplement using extract_arg_const.


Summary of changes:
 gdb/ChangeLog       |    7 +++++++
 gdb/cli/cli-utils.c |   25 +++++++++++++++++--------
 gdb/cli/cli-utils.h |    7 +++++++
 3 files changed, 31 insertions(+), 8 deletions(-)

gdb and binutils

                 reply	other threads:[~2013-11-14 10:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).