From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>,
Kevin Buettner <kevinb@redhat.com>,
gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@sourceware.org>
Subject: Re: [review] Add gdb_compile_openmp to lib/gdb.exp
Date: Wed, 06 Nov 2019 16:31:00 -0000 [thread overview]
Message-ID: <53a5f406-eb17-ba39-8168-0bcb161759b3@redhat.com> (raw)
In-Reply-To: <43214671-df5a-767e-39cc-cc0af512d85e@polymtl.ca>
[gerrit removed]
On 11/6/19 4:26 PM, Simon Marchi wrote:
> On 2019-11-06 11:24 a.m., Pedro Alves (Code Review) wrote:
>>>> (I wanted to select all lines from 5930 to 5961 to show the whole context in the email notificatio [â¦]
>>
>> Nice, that worked! I think it would be a good idea to mention this in our Gerrit wiki, to invite/remind people do this?
>
> Sure!
>
> (This is sent as an email to test replying to comments by email)
The handling for TABs makes the indentation levels hard to follow, though:
https://sourceware.org/ml/gdb-patches/2019-11/msg00168.html
Should the email notification replace tabs with 8 spaces?
Thanks,
Pedro Alves
next prev parent reply other threads:[~2019-11-06 16:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 4:26 Kevin Buettner (Code Review)
2019-11-05 15:27 ` Tom Tromey (Code Review)
2019-11-06 0:33 ` Pedro Alves (Code Review)
2019-11-06 16:09 ` Simon Marchi (Code Review)
2019-11-06 16:19 ` Pedro Alves (Code Review)
2019-11-06 16:24 ` Pedro Alves (Code Review)
2019-11-06 16:26 ` Simon Marchi
2019-11-06 16:31 ` Pedro Alves [this message]
2019-11-06 16:28 ` Simon Marchi
2019-11-06 16:29 ` Simon Marchi (Code Review)
2019-11-06 23:05 ` Kevin Buettner (Code Review)
2019-11-08 15:06 ` Pedro Alves
2019-11-06 23:14 ` Kevin Buettner (Code Review)
2019-11-09 20:59 ` [review v2] " Kevin Buettner (Code Review)
2019-12-03 16:41 ` Pedro Alves (Code Review)
2019-12-10 22:46 ` [pushed] " Sourceware to Gerrit sync (Code Review)
2019-12-10 22:46 ` 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=53a5f406-eb17-ba39-8168-0bcb161759b3@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
--cc=simon.marchi@polymtl.ca \
--cc=tromey@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