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 the "Start of New Year Procedure"
Date: Fri, 01 Jan 2010 10:42:00 -0000	[thread overview]
Message-ID: <83eimaf6k7.fsf@gnu.org> (raw)
In-Reply-To: <20100101091009.GI548@adacore.com>

> Date: Fri, 1 Jan 2010 13:10:09 +0400
> From: Joel Brobecker <brobecker@adacore.com>
> 
> I would like to clarify a little bit the process needed to update
> the copyright headers. Patch attached.

Thanks.

> +Run the @code{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.

It's better to put copyright.sh in @file, not in @code.

> +@itemize @bullet
> +  @item @file{*.s}
> +  @item @file{*.f}
> +  @item @file{*.f90}
> +  @item @file{*.igen}
> +  @item @file{*.ac}
> +  @item @file{*.texi}
> +  @item @file{*.texinfo}
> +  @item @file{*.tex}
> +  @item @file{*.defs}
> +  @item @file{*.1}
> +@end itemize

Although this format is permitted, the canonical way of writing an
itemized list is to have @item on its own line:

  @item
  @file{*.s}
  @item
  @file {*.f}
  ...

Did you have a good reason for not using the canonical form?  If not,
I'd prefer to use it, although I won't object to what you did as well.

Also, perhaps it is worthwhile to spell out the language for each file
type.  Again, that's not a blocking comment.

Otherwise, okay with me.


  reply	other threads:[~2010-01-01 10:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-01  9:10 Joel Brobecker
2010-01-01 10:42 ` Eli Zaretskii [this message]
2010-01-01 11:41   ` Joel Brobecker
  -- strict thread matches above, loose matches on Subject: below --
2009-01-06  5:03 [RFA/doco] Update the ``Start of New Year Procedure'' Joel Brobecker
2009-01-06  6:36 ` Daniel Jacobowitz
2009-01-07  4:43   ` 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=83eimaf6k7.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