On 15/02/17 11:12, Marek Polacek wrote: > On Wed, Feb 15, 2017 at 11:01:16AM +0000, Richard Earnshaw (lists) wrote: >> On 13/01/17 12:19, Torsten Duwe wrote: >>> Changes since v4: hopefully addressed all of Sandra's requests >>> and suggestions concerning the documentation snippets, thanks >>> for the feedback. If it still isn't clear, feel free to rephrase >>> -- I'm a programmer, not a technical writer. >>> >> >> Generally, I find 'pad' somewhat confusing. It's OK for the option name >> itself, but more generally, we should be talking about either space or >> number of instructions according to context. >> >>> 2017-01-13 Torsten Duwe <d...@suse.de> : >> >> Two spaces between date and name, two more between name and email, no >> colon at the end. >> >>> >>> * c-family/c-attribs.c : introduce prolog_pad attribute and create >>> a handler for it. >>> >> >> >> Don't leave blank lines between files mentioned here. All lines should >> be indented by /exactly/ one tab; don't add extra indentation for >> continuation lines. No space before colon. Capital letter at start of >> sentences, full stop at the end of each one. Which function, or data >> structure did you change (put the name in brackets before the colon)? >> Document each function or variable changed. >> >> The above entry should read: >> >> * c-family/c-attribs.c (c_common_attribute_table): Add entry >> for "prolog_pad". >> (handle_prolog_pad_attribute): New function. > > Except that the c-family/ prefix shouldn't be there. >
Ah, I'd missed that it has its own ChangeLog file and thus needs to be recorded separately. Ergo, the LTO entry can't use Likewise since the context for that will not be immediately above that entry... R. > Marek >
