From: Joseph Myers <joseph@codesourcery.com>
To: James Greenhalgh <james.greenhalgh@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"gerald@pfeifer.com" <gerald@pfeifer.com>
Subject: Re: [Patch docs 0/5] Update some of md.texi
Date: Tue, 06 Jan 2015 18:46:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.10.1501061844190.5282@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20150106152620.GA24397@arm.com>
On Tue, 6 Jan 2015, James Greenhalgh wrote:
> > and "Update text." is thoroughly unhelpful as a ChangeLog entry to
> > explain the intent of the changes.
>
> Well, indeed, but ChangeLog entries have always been a
> thoroughly unhelpful "what changed" rather than "why did it
> change". (grep ": Update\." gcc/ChangeLog*) !
That should be for cases where it's e.g. a completely mechanical change
following from a more fully described change to a file listed earlier in
the ChangeLog entry. For this sort of documentation patch, "what changed"
should be more specific (e.g. if you're updating the description of passes
to refer to gimplification then say so in the ChangeLog entry).
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2015-01-06 18:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 11:21 James Greenhalgh
2015-01-06 11:22 ` [Patch docs 3/5] Update "RTL Template" in md.texi James Greenhalgh
2015-01-12 22:04 ` Jeff Law
2015-01-12 22:11 ` Richard Sandiford
2015-01-06 11:22 ` [Patch docs 1/5] Update the first section of md.texi James Greenhalgh
2015-01-06 16:56 ` James Greenhalgh
2015-01-06 18:55 ` Joseph Myers
2015-01-08 21:43 ` Jeff Law
2015-01-09 2:11 ` Segher Boessenkool
2015-01-12 22:29 ` Richard Sandiford
2015-01-06 11:22 ` [Patch docs 4/5] Update "Output Template/Statement" from md.texi James Greenhalgh
2015-01-12 21:46 ` Jeff Law
2015-01-12 22:19 ` Richard Sandiford
2015-01-06 11:22 ` [Patch docs 2/5] Update "Instruction Patterns" in md.texi James Greenhalgh
2015-01-08 22:00 ` Jeff Law
2015-01-09 2:19 ` Segher Boessenkool
2015-01-11 17:40 ` James Greenhalgh
2015-01-12 22:31 ` Richard Sandiford
2015-01-06 11:23 ` [Patch docs 5/5] Update "Predicates" from md.texi James Greenhalgh
2015-01-12 22:42 ` Richard Sandiford
2015-01-06 14:57 ` [Patch docs 0/5] Update some of md.texi Joseph Myers
2015-01-06 15:26 ` James Greenhalgh
2015-01-06 17:31 ` Sandra Loosemore
2015-01-06 18:46 ` Joseph Myers [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=alpine.DEB.2.10.1501061844190.5282@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=james.greenhalgh@arm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).