Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Pedro Alves <palves@redhat.com>,
	gdb-patches@sourceware.org,
	       Aleksandar Ristovski <ARistovski@qnx.com>
Subject: Re: [patchv3 0/8] Validate binary before use
Date: Mon, 10 Mar 2014 10:12:00 -0000	[thread overview]
Message-ID: <20140310101156.GA17832@host2.jankratochvil.net> (raw)
In-Reply-To: <20140310095719.GB4882@adacore.com>

On Mon, 10 Mar 2014 10:57:19 +0100, Joel Brobecker wrote:
> > > >> These need to be 2013-2014.
> > > > 
> > > > Why?  It counts since the first post to gdb-patches?
> > > 
> > > https://sourceware.org/ml/gdb-patches/2014-02/msg00859.html
> > 
> > Do you mean this part?
> > #  1. We start claiming copyright the year the file as committed
> > #     to a medium (hard drive), not the year it was published.
> > 
> > Does "medium" mean any disk even unrelated to the GDB project?
> > Or does "medium" mean "any medium used for GDB development"?
> 
> Sorry, Jan - I don't know the answer to Jan's question, whether
> there is a distinction between the two situations. It doesn't seem
> like we need the answer in the context of that patch, but perhaps
> we could ask copyright-clerk if we want to satisfy our curiosity?

OK, so we do not know whether copyright year is affected by "any disk even
unrelated to the GDB project".

But gdb-patches mailing list was considered as a "medium (hard drive)"
mentioned by the copyright-clerk, IIUC.


Thanks,
Jan


  reply	other threads:[~2014-03-10 10:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-27 21:33 Jan Kratochvil
2014-02-28 13:47 ` Pedro Alves
2014-02-28 14:17   ` Aleksandar Ristovski
2014-03-02 18:37   ` Jan Kratochvil
2014-03-03 13:27     ` Pedro Alves
2014-03-08 17:33       ` Jan Kratochvil
2014-03-10  9:57         ` Joel Brobecker
2014-03-10 10:12           ` Jan Kratochvil [this message]
2014-03-10 14:27         ` 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=20140310101156.GA17832@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=ARistovski@qnx.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@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