Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: binutils@sourceware.org, gdb-patches@sourceware.org,
	gcc-patches@gcc.gnu.org
Subject: Re: copyright dates in binutils (and includes/)
Date: Thu, 27 Feb 2014 13:25:00 -0000	[thread overview]
Message-ID: <20140227132551.GO4348@adacore.com> (raw)
In-Reply-To: <20140227045011.GC14922@bubble.grove.modra.org>

Hi Alan,

My two cents...

> --- a/bfd/elf32-sparc.c
> +++ b/bfd/elf32-sparc.c
> @@ -1,7 +1,5 @@
>  /* SPARC-specific support for 32-bit ELF
> -   Copyright 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
> -   2003, 2004, 2005, 2006, 2007, 2010, 2011
> -   Free Software Foundation, Inc.
> +   Copyright (C) 1993-2014 Free Software Foundation, Inc.
>  
>     This file is part of BFD, the Binary File Descriptor library.
>  
> Does anyone have a violent objection to committing updates in
> bfd, binutils, elfcpp, gas, gold, gprof, ld, and opcodes?

FWIW, I find that the new ouptut is a nice improvement.

I should mention, however, that for us to use ranges like this,
the FSF asked us to add a note explaining that the copyright years
could be abbreviated into a range. See gdb/README (at the end).
I suspect that you'll need the same note for binutils.

> How about includes/ too?  The choices there are
> a) apply to just binutils owned files, 
> b) apply to binutils+gdb files,
> c) apply to the lot, and update gcc/include/ too.
> 
> I see Joel already updated include/gdb, but the script makes a further
> small change.  So choice (b) in include/gdb consists of patches like
> the following:

IIRC, the FSF does not require the (C), but I think they would
prefer it. Either way, it doesn't get in the way for future updates,
so I'd go with at least (b).

As for (c), I'll let the GCC folks answer.

-- 
Joel


  reply	other threads:[~2014-02-27 13:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-27  4:50 Alan Modra
2014-02-27 13:25 ` Joel Brobecker [this message]
2014-02-27 18:47   ` Joseph S. Myers
2014-02-28  8:57     ` Alan Modra
2014-02-28 13:08       ` Joel Brobecker
2014-02-28 18:22         ` Joseph S. Myers
2014-03-03  3:45           ` Alan Modra
2014-03-03  4:16             ` Alan Modra
2014-03-03 13:33               ` Richard Sandiford
2014-03-05 12:34                 ` Alan Modra

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=20140227132551.GO4348@adacore.com \
    --to=brobecker@adacore.com \
    --cc=binutils@sourceware.org \
    --cc=gcc-patches@gcc.gnu.org \
    --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