From: Joel Brobecker <brobecker@adacore.com>
To: Richard Earnshaw <rearnsha@arm.com>
Cc: Sergio Durigan Junior <sergiodj@redhat.com>,
Marcus Shawcroft <Marcus.Shawcroft@arm.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] aarch64-tdep basic port.
Date: Wed, 23 Jan 2013 11:13:00 -0000 [thread overview]
Message-ID: <20130123111245.GA14193@adacore.com> (raw)
In-Reply-To: <50FFB0C0.9060507@arm.com>
> I don't think so. Just because they haven't been committed to the
> FSF repository doesn't mean that earlier copyright dates don't also
> apply.
Richard is correct. According to an answer I got from the FSF, the
important date is when the code was committed to medium (HD).
--
Joel
next prev parent reply other threads:[~2013-01-23 11:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 17:39 Marcus Shawcroft
2013-01-23 5:21 ` Sergio Durigan Junior
2013-01-23 9:43 ` Richard Earnshaw
2013-01-23 11:13 ` Joel Brobecker [this message]
2013-01-24 20:03 ` Pedro Alves
2013-01-25 13:54 Marcus Shawcroft
2013-01-25 17:59 ` Pedro Alves
2013-01-25 18:55 ` Marcus Shawcroft
2013-01-25 18:59 ` Pedro Alves
2013-01-25 19:00 ` Marcus Shawcroft
2013-01-28 9:54 Marcus Shawcroft
2013-02-01 14:52 ` Pedro Alves
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=20130123111245.GA14193@adacore.com \
--to=brobecker@adacore.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=rearnsha@arm.com \
--cc=sergiodj@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