Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/doco] Update copyright year in refcard
Date: Fri, 01 Jan 2010 12:07:00 -0000	[thread overview]
Message-ID: <83aawyf2lk.fsf@gnu.org> (raw)
In-Reply-To: <20100101113041.GU2788@adacore.com>

> Date: Fri, 1 Jan 2010 15:30:41 +0400
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
> 
> That still leaves me
> wondering what should be done for the copyright notice in manuals, or
> the copyright year printed by GDB, gdbserver, etc. I believe that GDB
> does the right thing, and just prints the current year.  It is not
> so bad if it's a few years, but it looks a bit silly when the list
> spans an entirely line or more... I looked at a few manuals,
> particularly the ones that got reprinted, and they seem to follow
> a convention where the print one line per reprint, something like:
> 
>     (c) 2004 This Press Ltd
>     (c) 2006 This Press Ltd
>     (c) 2008 A Better Press And Sons Ltd
> 
> I'm happy to follow whatever the FSF dictates, but it would be nice
> if we could simply have just the current year in our manuals.

The year in the printed manual is a separate issue.  I don't know
about that, I think we should ask if we are unsure.

I was talking only about copyright notices on files we distribute, be
it part of the manual sources, the GDB sources, or whatever.


      reply	other threads:[~2010-01-01 12:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-01  9:18 Joel Brobecker
2010-01-01 10:47 ` Eli Zaretskii
2010-01-01 11:31   ` Joel Brobecker
2010-01-01 12:07     ` Eli Zaretskii [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=83aawyf2lk.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --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