public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Fix comment in field_kind
Date: Thu, 19 Dec 2019 18:32:00 -0000	[thread overview]
Message-ID: <2032eb7e934e65ab071f2a6ee8ce92327715d01d@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 2032eb7e934e65ab071f2a6ee8ce92327715d01d ***

commit 2032eb7e934e65ab071f2a6ee8ce92327715d01d
Author:     Tom Tromey <tromey@adacore.com>
AuthorDate: Thu Dec 19 11:12:29 2019 -0700
Commit:     Tom Tromey <tromey@adacore.com>
CommitDate: Thu Dec 19 11:12:29 2019 -0700

    Fix comment in field_kind
    
    Christian pointed out that the new comment in field_kind is
    un-grammatical.  This fixes it.
    
    gdb/ChangeLog
    2019-12-19  Tom Tromey  <tromey@adacore.com>
    
            * ui-out.h (enum class field_kind): Fix comment.
    
    Change-Id: I6608ff18e29f1af98a0ff77012afe28b3d4602f4

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 532dc6373a..aad9c632bb 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2019-12-19  Tom Tromey  <tromey@adacore.com>
+
+	* ui-out.h (enum class field_kind): Fix comment.
+
 2019-12-11  Tom Tromey  <tromey@adacore.com>
 
 	* xml-support.c (xml_fetch_content_from_file): Use FOPEN_RB.
diff --git a/gdb/ui-out.h b/gdb/ui-out.h
index c3ef8a5700..a176e0e797 100644
--- a/gdb/ui-out.h
+++ b/gdb/ui-out.h
@@ -77,9 +77,9 @@ enum ui_out_type
 /* The possible kinds of fields.  */
 enum class field_kind
   {
-    /* "FIELD_STRING" needs has a funny name to avoid clashes with
-       tokens named "STRING".  See PR build/25250.  FIELD_SIGNED is
-       given a similar name for consistency.  */
+    /* "FIELD_STRING" needs a funny name to avoid clashes with tokens
+       named "STRING".  See PR build/25250.  FIELD_SIGNED is given a
+       similar name for consistency.  */
     FIELD_SIGNED,
     FIELD_STRING,
   };


             reply	other threads:[~2019-12-19 18:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-19 18:32 gdb-buildbot [this message]
2019-12-19 18:44 ` Failures on Ubuntu-Aarch64-m64, branch master gdb-buildbot
2019-12-19 19:36 ` Failures on Ubuntu-Aarch64-native-gdbserver-m64, " gdb-buildbot
2019-12-20 19:03 ` Failures on Fedora-i686, " gdb-buildbot
2019-12-20 19:19 ` Failures on Fedora-x86_64-m32, " gdb-buildbot
2019-12-20 19:25 ` Failures on Fedora-x86_64-m64, " gdb-buildbot
2019-12-20 19:30 ` Failures on Fedora-x86_64-cc-with-index, " gdb-buildbot
2019-12-20 20:04 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2019-12-20 20:16 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2019-12-20 20:23 ` Failures on Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot

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=2032eb7e934e65ab071f2a6ee8ce92327715d01d@gdb-build \
    --to=gdb-buildbot@sergiodj.net \
    --cc=gdb-testers@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).