From: "Paweł Wódkowski" <pwodkowski@pl.sii.eu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"Michał Urbański" <murbanski@pl.sii.eu>,
"Sebastian Basierski" <sbasierski@pl.sii.eu>,
"tim.wiederhake@intel.com" <tim.wiederhake@intel.com>,
"dragos.carciumaru@intel.com" <dragos.carciumaru@intel.com>,
"bernhard.heckel@intel.com" <bernhard.heckel@intel.com>
Subject: Re: [PATCH v2 7/7] Fortran: Document scope operator.
Date: Thu, 22 Nov 2018 16:14:00 -0000 [thread overview]
Message-ID: <3e9a09eabb61478d8fca4a03d0585a0f@pl.sii.eu> (raw)
In-Reply-To: <834lccjuil.fsf@gnu.org>
On 20.11.2018 04:30, Eli Zaretskii wrote:
>> From: Pawel Wodkowski <pwodkowski@pl.sii.eu>
>> Cc: tim.wiederhake@intel.com, dragos.carciumaru@intel.com, Bernhard Heckel <bernhard.heckel@intel.com>
>> Date: Mon, 19 Nov 2018 22:38:50 +0100
>>
>> From: Bernhard Heckel <bernhard.heckel@intel.com>
>>
>> Document scope operator in GDB manual.
>>
>> 2016-08-10 Bernhard Heckel <bernhard.heckel@intel.com>
>>
>> gdb/Changelog:
>> * doc/gdb.texinfo (Fortran Operators): Describe scope operator.
>>
>> Changes from V1 to V2:
>> refactored entry in texinfo file, updated commit message.
>
> OK for this part.
>
> Thanks.
>
This is our first steps in GDB community so thanks for review.
Are we OK to push to all these changes or we need to wait for someone
else to ack?
Pawel
next prev parent reply other threads:[~2018-11-22 16:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 21:40 [PATCH v2 1/7] DWARF: Don't add nameless modules to partial symbol table Pawel Wodkowski
2018-11-19 21:40 ` [PATCH v2 5/7] Fortran: Enable setting breakpoint on nested functions Pawel Wodkowski
2018-11-28 10:32 ` Richard Bunt
2018-12-02 22:16 ` Paweł Wódkowski
2018-11-19 21:40 ` [PATCH v2 2/7] Dwarf: Fortran, support DW_TAG_entry_point Pawel Wodkowski
2018-11-27 22:09 ` Andrew Burgess
2018-12-02 21:32 ` Paweł Wódkowski
2018-11-19 21:40 ` [PATCH v2 6/7] Fortran: Nested functions, add scope parameter Pawel Wodkowski
2018-11-19 21:40 ` [PATCH v2 3/7] Fortran: Accessing fields of inherited types via fully qualified name Pawel Wodkowski
[not found] ` <88ec6786-8834-7da2-207a-7392fd657e41@arm.com>
[not found] ` <53cac622aea64147b2c1cd25feb16bdd@pl.sii.eu>
2018-12-06 15:03 ` Richard Bunt
2018-12-09 20:41 ` Paweł Wódkowski
2019-01-16 11:11 ` Richard Bunt
2019-01-18 8:33 ` Paweł Wódkowski
[not found] ` <9c1d974d-d5f3-93f7-12b0-0c95ac264cde@arm.com>
2019-02-06 12:39 ` Paweł Wódkowski
2018-11-19 21:40 ` [PATCH v2 4/7] Fortran: Ptype, print type extension Pawel Wodkowski
2019-02-01 13:06 ` Andrew Burgess
2018-11-19 21:40 ` [PATCH v2 7/7] Fortran: Document scope operator Pawel Wodkowski
2018-11-20 5:01 ` Eli Zaretskii
2018-11-22 16:14 ` Paweł Wódkowski [this message]
2018-11-23 10:31 ` Eli Zaretskii
2018-11-27 19:35 ` PING Re: [PATCH v2 1/7] DWARF: Don't add nameless modules to partial symbol table Pawel Wodkowski
2018-11-27 20:29 ` Simon Marchi
2018-11-27 21:42 ` Andrew Burgess
2018-12-02 21:01 ` Paweł Wódkowski
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=3e9a09eabb61478d8fca4a03d0585a0f@pl.sii.eu \
--to=pwodkowski@pl.sii.eu \
--cc=bernhard.heckel@intel.com \
--cc=dragos.carciumaru@intel.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=murbanski@pl.sii.eu \
--cc=sbasierski@pl.sii.eu \
--cc=tim.wiederhake@intel.com \
/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