From: Jim Blandy <jimb@redhat.com>
To: gdb@sources.redhat.com
Subject: ChangeLog entries for documentation
Date: Sun, 22 Dec 2002 15:03:00 -0000 [thread overview]
Message-ID: <vt23copn05v.fsf@zenia.red-bean.com> (raw)
(I expect this'll show up in the GNU coding standards pretty soon.)
------- Start of forwarded message -------
From: Richard Stallman <rms@gnu.org>
To: gnu-prog@gnu.org
Message-Id: <E18QEHo-00042d-00@fencepost.gnu.org>
Date: Sun, 22 Dec 2002 17:09:28 -0500
Subject: Change Logs
Reply-To: rms@gnu.org
X-Followup-Discussion-To: gnu-prog-discuss@gnu.org
In the past our policy was not to mention changes to documentation
files in ChangeLog, to save space. (Some people did not follow this
policy.)
I've been advised that for the sake of tracking copyrightable
contributions better we should start mentioning such changes
in ChangeLog files.
You need not go into much detail about what the change was. Just say
what part of the documentation file was changed (if it has parts and
the change was localized in one part), and whether the changes were
major or minor.
_______________________________________________
GNU Maintainers Announcement List gnu-prog@gnu.org
http://mail.gnu.org/mailman/listinfo/gnu-prog
------- End of forwarded message -------
next reply other threads:[~2002-12-22 23:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-22 15:03 Jim Blandy [this message]
2002-12-22 22:18 ` Eli Zaretskii
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=vt23copn05v.fsf@zenia.red-bean.com \
--to=jimb@redhat.com \
--cc=gdb@sources.redhat.com \
/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