From: Joel Brobecker <brobecker@adacore.com>
To: Siva Chandra <sivachandra@google.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [Patch v8] Debug methods using GDB Python
Date: Tue, 28 Jan 2014 11:58:00 -0000 [thread overview]
Message-ID: <20140128115824.GF4101@adacore.com> (raw)
In-Reply-To: <CAGyQ6gz9_qjtiGu9dpUFAx_U+DoDq+4_nrhPMzzk_5HkBqDJug@mail.gmail.com>
> I have fixed it locally now. Should come out correctly in v9.
[...]
> None of the new files were committed to the repo ever. But, most of
> them were posted for review in 2013. Should they still have 2013-2014
> range in the Copyright notice?
Yes, that's correct. When I asked the FSF about it, the answer was
that as long as it was saved somewhere, the range should include
that year. The year when it actually gets committed to the FSF
repo isn't really relevant in that case.
Thank you!
--
Joel
prev parent reply other threads:[~2014-01-28 11:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 11:19 Siva Chandra
2014-01-28 11:33 ` Joel Brobecker
2014-01-28 11:49 ` Siva Chandra
2014-01-28 11:58 ` Joel Brobecker [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=20140128115824.GF4101@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=sivachandra@google.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