From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org, brobecker@adacore.com
Subject: Re: [RFA/doco 3/3] Document new procedure for updating copyright years
Date: Wed, 04 Jan 2012 18:24:00 -0000 [thread overview]
Message-ID: <83mxa3pbtr.fsf@gnu.org> (raw)
In-Reply-To: <1325665146-31682-4-git-send-email-brobecker@adacore.com>
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: Joel Brobecker <brobecker@adacore.com>
> Date: Wed, 4 Jan 2012 12:19:06 +0400
>
> We now use a different script to perform the update. This patch
> updates the procedure in our documentation
>
> gdb/doc/ChangeLog:
>
> * gdbint.texinfo (Start of New Year Procedure): Update
> to replace use of copyright.sh by use of copyright.py.
>
> OK to commit?
Yes, with one comment:
> -Run the @file{copyright.sh} script to add the new year in the copyright
> -notices of most source files. This script requires Emacs 22 or later to
> -be installed.
> ...
> +Run the @file{copyright.py} Python script to add the new year in the copyright
> +notices of most source files.
Should we tell which versions of Python are required to run the
script, like the old text said about Emacs?
Thanks.
next prev parent reply other threads:[~2012-01-04 18:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 8:20 New " Joel Brobecker
2012-01-04 8:20 ` [RFA/doco 3/3] Document new " Joel Brobecker
2012-01-04 18:24 ` Eli Zaretskii [this message]
2012-01-05 3:34 ` Joel Brobecker
2012-01-05 5:44 ` Eli Zaretskii
2012-01-05 9:42 ` Joel Brobecker
2012-01-04 8:20 ` [commit 2/3] use gnulib's update-copyright script to update " Joel Brobecker
2012-01-04 8:20 ` [commit 1/3] Import gnulib's update-copyright script Joel Brobecker
2012-04-18 12:41 ` Pedro Alves
2012-04-18 14:37 ` Joel Brobecker
2012-04-18 14:52 ` Pedro Alves
2012-04-18 14:54 ` Joel Brobecker
2012-04-18 15:10 ` Pedro Alves
2012-04-18 15:12 ` Tom Tromey
2012-04-18 20:52 ` Import gnulib's update-copyright whole module Pedro Alves
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=83mxa3pbtr.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