From: "Tom de Vries (Code Review)" <gerrit@gnutoolchain-gerrit.osci.io>
To: Christian Biesinger <cbiesinger@google.com>, gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@polymtl.ca>
Subject: Change in binutils-gdb[master]: Load system gdbinit files from a directory
Date: Mon, 14 Oct 2019 20:01:00 -0000 [thread overview]
Message-ID: <20191014200123.610D829ECF@gnutoolchain-gerrit.osci.io> (raw)
In-Reply-To: <gerrit.1570968845000.If233859ecc21bc6421d589b37cd658a3c7d030f2@gnutoolchain-gerrit.osci.io>
Tom de Vries has posted comments on this change. ( https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/26 )
Change subject: Load system gdbinit files from a directory
......................................................................
Patch Set 1:
$ ../check_GNU_style.sh 0001-Load-system-gdbinit-files-from-a-directory.patch
Lines should not exceed 80 characters.
414:+ /* We effectively don't support "set script-extension off/soft",
422:+ sysgdbinit.insert (sysgdbinit.end (), files.begin (), files.end ());
Dot, space, space, end of comment.
78:+ moved. */
Sentences should end with a dot. Dot, space, space, end of the comment.
74:+/* automatically load system-wide gdbinit files from this directory */
There should be exactly one space between function name and parenthesis.
410:+ if (stat(filename.c_str (), &s) != 0 || !S_ISREG (s.st_mode))
--
To view, visit https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/26
To unsubscribe, or for help writing mail filters, visit https://gnutoolchain-gerrit.osci.io/r/settings
Gerrit-Project: binutils-gdb
Gerrit-Branch: master
Gerrit-Change-Id: If233859ecc21bc6421d589b37cd658a3c7d030f2
Gerrit-Change-Number: 26
Gerrit-PatchSet: 1
Gerrit-Owner: Christian Biesinger <cbiesinger@google.com>
Gerrit-CC: Simon Marchi <simon.marchi@polymtl.ca>
Gerrit-CC: Tom de Vries <tdevries@suse.de>
Gerrit-Comment-Date: Mon, 14 Oct 2019 20:01:23 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
next parent reply other threads:[~2019-10-14 20:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gerrit.1570968845000.If233859ecc21bc6421d589b37cd658a3c7d030f2@gnutoolchain-gerrit.osci.io>
2019-10-14 20:01 ` Tom de Vries (Code Review) [this message]
2019-10-16 22:18 ` [review] " Christian Biesinger (Code Review)
2019-10-17 7:00 ` Eli Zaretskii
2019-10-18 11:57 ` Christian Biesinger via gdb-patches
2019-10-16 22:18 ` Christian Biesinger (Code Review)
2019-10-16 22:19 ` Christian Biesinger (Code Review)
2019-10-17 0:34 ` Tom de Vries (Code Review)
2019-10-18 11:57 ` Christian Biesinger (Code Review)
2019-10-23 14:56 ` [review v4] " Christian Biesinger (Code Review)
2019-10-23 14:56 ` Christian Biesinger (Code Review)
2019-10-24 18:59 ` Simon Marchi (Code Review)
2019-10-24 19:05 ` [review v5] " Christian Biesinger (Code Review)
2019-10-24 19:05 ` Christian Biesinger (Code Review)
2019-10-25 15:04 ` Tom Tromey (Code Review)
2019-10-29 18:35 ` Simon Marchi (Code Review)
2019-10-29 18:52 ` [pushed] " Sourceware to Gerrit sync (Code Review)
2019-10-29 18:52 ` Sourceware to Gerrit sync (Code Review)
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=20191014200123.610D829ECF@gnutoolchain-gerrit.osci.io \
--to=gerrit@gnutoolchain-gerrit.osci.io \
--cc=cbiesinger@google.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
--cc=tdevries@suse.de \
/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