Re: broken check: You should edit tm.texi.in rather than tm.texi

2020-11-23 Thread Martin Sebor via Gcc
On 11/23/20 1:25 PM, Joseph Myers wrote: On Mon, 23 Nov 2020, Martin Sebor via Gcc wrote: I'd expect the best way to ensure the two copies of the contributed text are in sync is to copy it automatically. If the only point of asking the author to do it by hand each time they change the file is

Re: broken check: You should edit tm.texi.in rather than tm.texi

2020-11-23 Thread Joseph Myers
On Mon, 23 Nov 2020, Martin Sebor via Gcc wrote: > I'd expect the best way to ensure the two copies of the contributed > text are in sync is to copy it automatically. If the only point of > asking the author to do it by hand each time they change the file > is to "Verify that they have permission

Re: broken check: You should edit tm.texi.in rather than tm.texi

2020-11-23 Thread Martin Sebor via Gcc
On 11/23/20 12:45 PM, Joseph Myers wrote: On Mon, 23 Nov 2020, Martin Sebor via Gcc wrote: I never did understand what it was complaining about, or the point of making us jump through these hoops for updates to the internals manual when the (arguably far more impactful) changes to GCC source co

Re: broken check: You should edit tm.texi.in rather than tm.texi

2020-11-23 Thread Joseph Myers
On Mon, 23 Nov 2020, Martin Sebor via Gcc wrote: > I never did understand what it was complaining about, or the point > of making us jump through these hoops for updates to the internals > manual when the (arguably far more impactful) changes to GCC source > code or the user-visible manual aren't

Re: broken check: You should edit tm.texi.in rather than tm.texi

2020-11-23 Thread Martin Sebor via Gcc
On 11/20/20 6:23 AM, Martin Liška wrote: Hello. I hit the following issue: /bin/sh /home/marxin/Programming/gcc/gcc/../move-if-change tmp-tm.texi tm.texi You should edit /home/marxin/Programming/gcc/gcc/doc/tm.texi.in rather than /home/marxin/Programming/gcc/gcc/doc/tm.texi . Steps to reprod

Re: broken check: You should edit tm.texi.in rather than tm.texi

2020-11-20 Thread H.J. Lu via Gcc
On Fri, Nov 20, 2020 at 7:26 AM Martin Liška wrote: > > On 11/20/20 2:42 PM, H.J. Lu wrote: > > Should contrib/gcc_update handle it? > > I don't know how publicly known is the script? > I personally do not used it. > I always run $ ./contrib/gcc_update --touch after rebase. -- H.J.

Re: broken check: You should edit tm.texi.in rather than tm.texi

2020-11-20 Thread Martin Liška
On 11/20/20 4:26 PM, Martin Liška wrote: On 11/20/20 2:42 PM, H.J. Lu wrote: Should contrib/gcc_update handle it? I don't know how publicly known is the script? I personally do not used it. Martin ... or we can add a hint: diff --git a/gcc/Makefile.in b/gcc/Makefile.in index 778ec09c75d..f

Re: broken check: You should edit tm.texi.in rather than tm.texi

2020-11-20 Thread Martin Liška
On 11/20/20 2:42 PM, H.J. Lu wrote: Should contrib/gcc_update handle it? I don't know how publicly known is the script? I personally do not used it. Martin

Re: broken check: You should edit tm.texi.in rather than tm.texi

2020-11-20 Thread H.J. Lu via Gcc
On Fri, Nov 20, 2020 at 5:24 AM Martin Liška wrote: > > Hello. > > I hit the following issue: > /bin/sh /home/marxin/Programming/gcc/gcc/../move-if-change tmp-tm.texi tm.texi > You should edit /home/marxin/Programming/gcc/gcc/doc/tm.texi.in rather than > /home/marxin/Programming/gcc/gcc/doc/tm.te