Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Update copyright dates in gdb.texinfo
Date: Fri, 31 Mar 2006 22:19:00 -0000	[thread overview]
Message-ID: <442D8748.5020502@redhat.com> (raw)
In-Reply-To: <uwteaaf29.fsf@gnu.org>

Eli Zaretskii wrote:
>>Date: Fri, 31 Mar 2006 08:55:51 -0500
>>From: Daniel Jacobowitz <drow@false.org>
>>Cc: Michael Snyder <msnyder@redhat.com>, gdb-patches@sources.redhat.com
>>
>>
>>>Yes, thanks.  But I thought we all agreed that copyright years need to
>>>be changed only as part of preparing a release, and that at that time
>>>all files need to be stamped with the release year.  Did I miss
>>>something?
>>
>>Isn't it the other way around?
> 
> 
> I didn't think it was.
> 
> Anyone, this is nothing worth arguing about.
> 

Anyway, committed.
Thanks.


      reply	other threads:[~2006-03-31 19:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-31  8:03 Michael Snyder
2006-03-31 10:40 ` Eli Zaretskii
2006-03-31 19:47   ` Daniel Jacobowitz
2006-03-31 22:17     ` Eli Zaretskii
2006-03-31 22:19       ` Michael Snyder [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=442D8748.5020502@redhat.com \
    --to=msnyder@redhat.com \
    --cc=eliz@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