public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: "Willgerodt, Felix" <felix.willgerodt@intel.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [Ping] [PATCH] gdb, testsuite: Fix mi-var-child-f.exp for Intel compilers.
Date: Tue, 25 May 2021 08:18:06 -0700	[thread overview]
Message-ID: <f342ccd5-71c3-6a61-2936-0d738e19e81f@redhat.com> (raw)
In-Reply-To: <1b811290a1b040608740d773dbfef25a@intel.com>

On 5/25/21 1:25 AM, Willgerodt, Felix wrote:
> I don't think I understand your question. Afaik git mv doesn't add
> anything in regards to file tracking compared to mv.

I guess my confusion stems from the copyright range listed in gdb.mi/array.f90:

> +! Copyright 2006-2021 Free Software Foundation, Inc.

I'm not sure what this is meant to convey. However, git shows:

> $ git log --oneline --follow -- gdb/testsuite/gdb.mi/array.f90
> 048a4177f6a (HEAD -> up/fortran) gdb, testsuite: Fix mi-var-child-f.exp for Intel compilers.
> 3666a048837 Update copyright year range in all GDB files
> b811d2c2920 Update copyright year range in all GDB files.
> 42a4f53d2bf Update copyright year range in all GDB files.
> ...

that the file's history is preserved, so that's all I wanted to ensure,
however that was accomplished.

In short, (still) LGTM.

Keith


      reply	other threads:[~2021-05-25 15:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-21  6:52 Willgerodt, Felix
2021-05-24 20:58 ` Keith Seitz
2021-05-25  8:25   ` Willgerodt, Felix
2021-05-25 15:18     ` Keith Seitz [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=f342ccd5-71c3-6a61-2936-0d738e19e81f@redhat.com \
    --to=keiths@redhat.com \
    --cc=felix.willgerodt@intel.com \
    --cc=gdb-patches@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).