Hi, If we are good at this point, could someone help with merging it? (I don’t have commit access, of course.)
Sergey On Aug 14, 2024 at 21:30 +0800, Sergey Fedorov <vital....@gmail.com>, wrote: > Thank you, Iain. > I have adjusted a longer line and added an intro sentence before changelog > record. > > > > > On Wed, Aug 14, 2024 at 8:24 PM Iain Sandoe <idsan...@googlemail.com> wrote: > > > > > > > > > > On 14 Aug 2024, at 13:17, Sergey Fedorov <vital....@gmail.com> wrote: > > > > > > > > > > > > > > > > On Wed, Aug 14, 2024 at 8:03 PM FX Coudert <fxcoud...@gmail.com> wrote: > > > > > Thank you for responding. > > > > > I have added a changelog (is this a correct way?). > > > > > > > > Content seems ok, lines are maybe too long. Check with > > > > contrib/gcc-changelog/git_check_commit.py before pushing. > > > > Once that is fine, OK to push. > > > > > > > > Looks like the script is okay with formatting: > > > > > > > > 36-25% /opt/local/bin/python3.11 > > > > /Users/svacchanda/Github_barracuda156/gcc-git/contrib/gcc-changelog/git_check_commit.py > > > > Checking 16e8ea376ada59306583decf1a218b2281a48638: OK > > > > > > * config/fpu-macppc.h (new file): initial support for > > > powerpc-darwin. > > > * configure.host: enable ieee_support for powerpc-darwin case, > > > set fpu_host='fpu-macppc’. > > > > > > The description lines should begin with a capital letter and the lines > > > should > > > not exceed 80 chars (some people prefer if they do not exceed 76 chars so > > > that “git show” output fits into 80 columns). > > > > > > hth > > > Iain > > > > > > > > > > > > > > Sergey > > > > > > >