public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/18033] C++ style comment used in iq2000-tdep.c
Date: Thu, 26 Feb 2015 15:14:00 -0000	[thread overview]
Message-ID: <bug-18033-4717-LVjX28DHyj@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18033-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=18033

--- Comment #5 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The gdb-7.9-branch branch has been updated by Jan Kratochvil
<jkratoch@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=09de64b93c2402e068daf0bce1c4a1dda833b646

commit 09de64b93c2402e068daf0bce1c4a1dda833b646
Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Date:   Thu Feb 26 11:52:28 2015 +0100

    Change // comment in gdb/compile/

    gdb/ChangeLog
    2015-02-26  Jan Kratochvil  <jan.kratochvil@redhat.com>

        PR build/18033
        * compile/compile-c-support.c (c_compute_program): Change // comment.
        * compile/compile-object-load.c (setup_sections): Change // comment.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2015-02-26 10:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-26  9:43 [Bug build/18033] New: " brobecker at gnat dot com
2015-02-26  9:45 ` [Bug build/18033] " cvs-commit at gcc dot gnu.org
2015-02-26  9:48 ` cvs-commit at gcc dot gnu.org
2015-02-26 10:51 ` brobecker at gnat dot com
2015-02-26 10:53 ` cvs-commit at gcc dot gnu.org
2015-02-26 15:14 ` cvs-commit at gcc dot gnu.org [this message]
2015-02-26 19:42 ` [Bug build/18033] C++ style comment used in gdb/iq2000-tdep.c and gdb/compile/compile-*.c brobecker at gnat dot com

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=bug-18033-4717-LVjX28DHyj@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).