On Sat, Sep 14, 2019 at 5:35 AM Gavin Smith wrote:
> On Mon, Sep 2, 2019 at 6:28 PM Jim Meyering wrote:
> >
> > Gavin Smith proposed a patch for this back in http://bugs.gnu.org/34201
> > Another reference to the problem: http://bugs.gnu.org/36921
> >
> > In the attached (in Gavin's name), I've a
On Mon, Sep 2, 2019 at 6:28 PM Jim Meyering wrote:
>
> Gavin Smith proposed a patch for this back in http://bugs.gnu.org/34201
> Another reference to the problem: http://bugs.gnu.org/36921
>
> In the attached (in Gavin's name), I've added a NEWS entry and
> adjusted the ChangeLog entry. Will push
Hello Jim,
Jim Meyering writes:
> Gavin Smith proposed a patch for this back in http://bugs.gnu.org/34201
> Another reference to the problem: http://bugs.gnu.org/36921
>
> In the attached (in Gavin's name), I've added a NEWS entry and
> adjusted the ChangeLog entry. Will push in a day or so if n
Is there anybody who has time to look at this issue? The requirement
for a @setfilename line is an unnecessary hurdle to getting Texinfo
and Automake working together. It has been unnecessary for several
years now.
I have a copyright assignment in place for Automake with the FSF, so
all that would
@setfilename should not be required to occur inside Texinfo files, as it
makes it harder to get them working.
Earlier on this:
https://lists.gnu.org/archive/html/automake/2015-09/msg0.html
Here is a patch. I added a test which is passing now, but it wasn't
passing when I first added the te
