From: Siva Chandra <sivachandra@google.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [Patch v8] Debug methods using GDB Python
Date: Tue, 28 Jan 2014 11:49:00 -0000 [thread overview]
Message-ID: <CAGyQ6gz9_qjtiGu9dpUFAx_U+DoDq+4_nrhPMzzk_5HkBqDJug@mail.gmail.com> (raw)
In-Reply-To: <20140128113253.GE4101@adacore.com>
On Tue, Jan 28, 2014 at 3:32 AM, Joel Brobecker <brobecker@adacore.com> wrote:
> copyright years in the copyright range are not always including 2014.
I have fixed it locally now. Should come out correctly in v9.
> Also, for those which do have 2014, the range of years should start
> with the year the file was first committed to medium. So if you
> started working on a given file the year before, the Copyright year
> should be 2013-2014 (please always use a single range).
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?
next prev parent reply other threads:[~2014-01-28 11:49 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 [this message]
2014-01-28 11:58 ` Joel Brobecker
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=CAGyQ6gz9_qjtiGu9dpUFAx_U+DoDq+4_nrhPMzzk_5HkBqDJug@mail.gmail.com \
--to=sivachandra@google.com \
--cc=brobecker@adacore.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