public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@ericsson.com>
To: <gdb-patches@sourceware.org>
Cc: Simon Marchi <simon.marchi@ericsson.com>
Subject: [PATCH obvious/pushed] Remove duplicate comment
Date: Mon, 01 Dec 2014 14:15:00 -0000	[thread overview]
Message-ID: <1417443293-398-1-git-send-email-simon.marchi@ericsson.com> (raw)

I took the liberty of pushing this under the obvious rule. Hopefully, I did not
mess up anything.

gdb/ChangeLog:

	* objfiles.c (allocate_objfile): Remove duplicate comment.
---
 gdb/ChangeLog  | 4 ++++
 gdb/objfiles.c | 4 ----
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index cfc41db..13346fa 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2014-12-01  Simon Marchi  <simon.marchi@ericsson.com>
+
+	* objfiles.c (allocate_objfile): Remove duplicate comment.
+
 2014-12-01  Ulrich Weigand  <uweigand@de.ibm.com>
 
 	* config/i386/i386gnu.mh (NATDEPFILES): Remove core-regset.o.
diff --git a/gdb/objfiles.c b/gdb/objfiles.c
index 5878add..a5df305 100644
--- a/gdb/objfiles.c
+++ b/gdb/objfiles.c
@@ -314,10 +314,6 @@ allocate_objfile (bfd *abfd, const char *name, int flags)
      that any data that is reference is saved in the per-objfile data
      region.  */
 
-  /* Update the per-objfile information that comes from the bfd, ensuring
-     that any data that is reference is saved in the per-objfile data
-     region.  */
-
   objfile->obfd = abfd;
   gdb_bfd_ref (abfd);
   if (abfd != NULL)
-- 
2.1.3

                 reply	other threads:[~2014-12-01 14:15 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:
  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=1417443293-398-1-git-send-email-simon.marchi@ericsson.com \
    --to=simon.marchi@ericsson.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).