GNU bug report logs - #68375
29.1; lispref documentation fixes

Previous Next

Full log

Message #25 received at 68375 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stephen Berman <stephen.berman <at> gmx.net>
Cc: 68375 <at> debbugs.gnu.org, manphiz <at> gmail.com
Subject: Re: bug#68375: 29.1; lispref documentation fixes
Date: Thu, 11 Jan 2024 16:56:13 +0200

> From: Stephen Berman <stephen.berman <at> gmx.net>
> Cc: eliz <at> gnu.org,  manphiz <at> gmail.com
> Date: Thu, 11 Jan 2024 15:32:10 +0100
> 
> On Thu, 11 Jan 2024 15:21:08 +0100 Stephen Berman <stephen.berman <at> gmx.net> wrote:
> 
> > On Thu, 11 Jan 2024 14:44:35 +0100 Stephen Berman <stephen.berman <at> gmx.net> wrote:
> >
> >> On Thu, 11 Jan 2024 12:46:34 +0200 Eli Zaretskii <eliz <at> gnu.org> wrote:
> >>
> >>>> From: Xiyue Deng <manphiz <at> gmail.com>
> >>>> Date: Wed, 10 Jan 2024 14:56:23 -0800
> >>>> 
> >>>> Please find the attached patches for a cumulation of documentation fixes
> >>>> for lispref up to chapter 19 that includes typos, formatting, etc.
> >>>> Please let me know if any changes need improvements and I'll adjust
> >>>> accordingly.
> >>>
> >>> Thanks.  See below.
> >> [...]
> >>>>    A string is a fixed sequence of characters.  It is a type of
> >>>> -sequence called a @dfn{array}, meaning that its length is fixed and
> >>>> +sequence called an @dfn{array}, meaning that its length is fixed and
> >>>
> >>> The "an" here is correct, since in a manual one sees "an array", which
> >>> is correct English.  So I didn't install this part.
> >>
> >> You misread the patch, it changes "a" to "an", which makes the text
> >> correct English.  I thought I'd save you some work by installing the
> >> patch myself, which I just did, but unfortunately to master instead of
> >> emacs-29 (and also forgot to add the bug number).  Should I revert it
> >> and install to the release branch?  Sorry for the trouble.
> >
> > I went ahead and reverted the change on master and installed it on
> > emacs-29 (with bug number).
> 
> ... but without the "Copyright-paperwork-exempt: yes" cookie 😕.  Should
> I revert again?  (This time I will not act without explicit permission.)

It's too late, since reverting a change doesn't remove it from Git
history.

I hope Xiyue Deng will assign the copyright, which will then cover
this blunder.

Thanks.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.