unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: don@donarmstrong.com (Emacs bug Tracking System)
To: Glenn Morris <rgm@gnu.org>
Subject: bug#1170: marked as done (23.0.60; emacs-lisp-intro.texi)
Date: Wed, 15 Oct 2008 21:15:03 -0700	[thread overview]
Message-ID: <handler.1170.D1170.122413016629525.ackdone@emacsbugs.donarmstrong.com> (raw)
In-Reply-To: 4135e3e50810141603y3df49946n283d72b1b77f76b9@mail.gmail.com

[-- Attachment #1: Type: text/plain, Size: 838 bytes --]


Your message dated Thu, 16 Oct 2008 00:06:48 -0400
with message-id <gybpxlb2uf.fsf@fencepost.gnu.org>
and subject line Re: bug#1170: 23.0.60; emacs-lisp-intro.texi
has caused the Emacs bug report #1170,
regarding 23.0.60; emacs-lisp-intro.texi
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact don@donarmstrong.com
immediately.)


-- 
1170: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=1170
Emacs Bug Tracking System
Contact don@donarmstrong.com with problems

[-- Attachment #2: Type: message/rfc822, Size: 3509 bytes --]

From: "Sean Sieger" <sean.sieger@gmail.com>
To: bug-gnu-emacs@gnu.org
Subject: 23.0.60; emacs-lisp-intro.texi
Date: Tue, 14 Oct 2008 19:03:10 -0400
Message-ID: <4135e3e50810141603y3df49946n283d72b1b77f76b9@mail.gmail.com>

* emacs-lisp-intro.texi: Fix typo on line 11528, change `assemblies'
  to `assembles'.


Section 11.3.3 Recursion with a List, paragraph 7 reads:

   Put in yet another way, if the list is not empty, the first robot
assemblies a second robot and tells it what to do; the second robot is
a different individual from the first, but is the same model.

it should read:

   Put in yet another way, if the list is not empty, the first robot
assembles a second robot and tells it what to do; the second robot is
a different individual from the first, but is the same model.




[-- Attachment #3: Type: message/rfc822, Size: 1641 bytes --]

From: Glenn Morris <rgm@gnu.org>
To: 1170-done@emacsbugs.donarmstrong.com
Subject: Re: bug#1170: 23.0.60; emacs-lisp-intro.texi
Date: Thu, 16 Oct 2008 00:06:48 -0400
Message-ID: <gybpxlb2uf.fsf@fencepost.gnu.org>

"Sean Sieger" wrote:

> * emacs-lisp-intro.texi: Fix typo on line 11528, change `assemblies'
>   to `assembles'.

Thanks; applied.


      reply	other threads:[~2008-10-16  4:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gybpxlb2uf.fsf@fencepost.gnu.org>
2008-10-14 23:03 ` bug#1170: 23.0.60; emacs-lisp-intro.texi Sean Sieger
2008-10-16  4:15   ` Emacs bug Tracking System [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=handler.1170.D1170.122413016629525.ackdone@emacsbugs.donarmstrong.com \
    --to=don@donarmstrong.com \
    --cc=rgm@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).