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 new-year checklist (was "Re: Need to update copyright year in sources & docs")
Date: Sat, 05 Jan 2008 11:07:00 -0000	[thread overview]
Message-ID: <u1w8wwmxw.fsf@gnu.org> (raw)
In-Reply-To: <20080102084609.GB15903@adacore.com> (message from Joel Brobecker 	on Wed, 2 Jan 2008 00:46:09 -0800)

> Date: Wed, 2 Jan 2008 00:46:09 -0800
> From: Joel Brobecker <brobecker@adacore.com>
> 
> I propose the following addition to gdbint.texi:
> 
> 2008-01-02  Joel Brobecker  <brobecker@adacore.com>
> 
>         * gdbint.texinfo (Start of New Year Procedure): Add item
>         describing how to update the source and documentation copyright
>         notices.

Thanks.

> Tested on x86-linux, by rebuilding the HTML documentation.
> OK to apply?

Yes, but first, please take care of these minor gotchas:

> +Add the new year in the copyright notice of all source and documentation

I think "notices" (plural) is more correct here.

> +files. This is done semi-automatically by running the @code{copyright.sh}
        ^^
Two spaces after the period that ends a sentence, please.  Also, "This
can be done" is probably better, since we don't want to _force_ use of
the script, do we?

> +script.  This script requires emacs 22 or later to be installed.

Emacs should be capitalized here.


  reply	other threads:[~2008-01-05 11:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-01  4:34 Need to update copyright year in sources & docs Joel Brobecker
2008-01-01 22:48 ` Daniel Jacobowitz
2008-01-02  8:46   ` [RFA/doco] Update new-year checklist (was "Re: Need to update copyright year in sources & docs") Joel Brobecker
2008-01-05 11:07     ` Eli Zaretskii [this message]
2008-01-05 15:16       ` Joel Brobecker

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=u1w8wwmxw.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