Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ijaz, Abdul B" <abdul.b.ijaz@intel.com>
To: Kevin Buettner <kevinb@redhat.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH v2 1/1] gdb, fortran: Fix local variable lookup in Fortran parser
Date: Mon, 4 May 2026 07:05:29 +0000	[thread overview]
Message-ID: <SA1PR11MB68469C566482172012DCA188CB312@SA1PR11MB6846.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20260501104740.68be17d8@f42-zbm-amd>

Thanks Kevin for the feedback.

>> +! along with this program.  If not, see <http://www.gnu.org/licenses/> .

Kevin>In the above line, there's a stray space before the period at the end of the line.

Abdul>I will fix it before merging.

Best Regards
Abdul Basit

-----Original Message-----
From: Kevin Buettner <kevinb@redhat.com> 
Sent: Friday, May 1, 2026 7:48 PM
To: gdb-patches@sourceware.org
Cc: Ijaz, Abdul B <abdul.b.ijaz@intel.com>
Subject: Re: [PATCH v2 1/1] gdb, fortran: Fix local variable lookup in Fortran parser

Hi Abdul,

One small nit, but otherwise it's okay...

On Thu, 30 Apr 2026 18:29:55 +0200
Abdul Basit Ijaz <abdul.b.ijaz@intel.com> wrote:

> +! along with this program.  If not, see <http://www.gnu.org/licenses/> .

In the above line, there's a stray space before the period at the end of the line.

With that fixed...

Approved-by: Kevin Buettner <kevinb@redhat.com>

Intel Deutschland GmbH
Registered Address: Dornacher Strasse 1, 85622 Feldkirchen, Germany
Tel: +49 89 991 430, www.intel.de
Managing Directors: Harry Demas, Jeffrey Schneiderman, Yin Chong Sorrell
Chairperson of the Supervisory Board: Nicole Lau
Registered Seat: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928

      reply	other threads:[~2026-05-04  7:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-30 16:29 [PATCH v2 0/1] " Abdul Basit Ijaz
2026-04-30 16:29 ` [PATCH v2 1/1] " Abdul Basit Ijaz
2026-05-01 17:47   ` Kevin Buettner
2026-05-04  7:05     ` Ijaz, Abdul B [this message]

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=SA1PR11MB68469C566482172012DCA188CB312@SA1PR11MB6846.namprd11.prod.outlook.com \
    --to=abdul.b.ijaz@intel.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@redhat.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