From: Tom Tromey <tom@tromey.com>
To: Jan Vrany <jan.vrany@fit.cvut.cz>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PING] [PATCH v5] Fix segfault when invoking -var-info-path-expression on a dynamic varobj
Date: Mon, 30 Jul 2018 16:49:00 -0000 [thread overview]
Message-ID: <878t5s655q.fsf@tromey.com> (raw)
In-Reply-To: <64280436fa39130ab3f567ce968a40d5f2f5ce62.camel@fit.cvut.cz> (Jan Vrany's message of "Wed, 25 Jul 2018 13:33:26 +0100")
>>>>> "Jan" == Jan Vrany <jan.vrany@fit.cvut.cz> writes:
Thanks for the patch.
>> + Copyright (C) 1999-2018 Free Software Foundation, Inc.
>> +# Copyright (C) 2008-2018 Free Software Foundation, Inc.
>> +# Copyright (C) 2008-2018 Free Software Foundation, Inc.
These dates look weird. I assume you copied the headers from elsewhere
-- a time-honored tradition. However if the files don't substantially
share anything with other files, I think just 2018 should suffice.
This is ok with this either fixed, or if there's some overlap, an email
to that effect.
Tom
next prev parent reply other threads:[~2018-07-30 16:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 19:21 Jan Vrany
2018-07-25 12:33 ` [PING] " Jan Vrany
2018-07-30 16:49 ` Tom Tromey [this message]
2018-07-30 19:53 ` Simon Marchi
2018-07-31 9:14 ` Jan Vrany
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=878t5s655q.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.vrany@fit.cvut.cz \
/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