Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: introduce SH 2a simulator
Date: Mon, 13 Sep 2004 17:39:00 -0000	[thread overview]
Message-ID: <or3c1mhxvv.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <412BABA3.7020300@gnu.org>

On Aug 24, 2004, Andrew Cagney <cagney@gnu.org> wrote:

> Can you revise the ChangeLogs as follows:

>> Index: include/gdb/ChangeLog
>> from  Alexandre Oliva  <aoliva@redhat.com>
>> 2004-02-13  Michael Snyder  <msnyder@redhat.com>
>> * sim-sh.h: Add new sh2a banked registers.

> Write this as

> YYYY-MM-DD  Michael Snyder ....

> 	Committed by ....
> 	* change.

> Rewrite the below as:

> YYYY-MM-DD  Michael Snyder ....

> 	Committed by ...
> 	* final set of changes

> instead of a long winded change history.

There's a good reason why I do it the way I posted it.  Neither of
your suggestions would be correct, copyright-wise.

The law in most countries extend the copyright from the time of
creation or first publishing, until a certain number of years after
that fact, or the last day of that year, or a certain number of years
after the author's death, or something along these lines.

The relevant point here is that, in several countries, it's important
to know, as accurately as possible, the date on which the code was
written.

This is why I retain the individual ChangeLog entries, with their
corresponding dates.  Checking the code in at a later time should not
automatically extend the period in which the code is covered by
copyright.

I do agree the format I use to that end is cumbersome, but I don't see
that any other format conveys the information that may be necessary in
case of a copyright dispute.

-- 
Alexandre Oliva             http://www.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}


      parent reply	other threads:[~2004-09-13 17:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-29  5:51 Alexandre Oliva
2004-08-24 20:58 ` Andrew Cagney
2004-09-07 15:33   ` Corinna Vinschen
2004-09-07 20:29     ` Andrew Cagney
2004-09-08  9:22       ` Corinna Vinschen
2004-09-13 17:39   ` Alexandre Oliva [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=or3c1mhxvv.fsf@free.redhat.lsd.ic.unicamp.br \
    --to=aoliva@redhat.com \
    --cc=cagney@gnu.org \
    --cc=gdb-patches@sources.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