all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ineiev <ineiev@gnu.org>
To: eliz via RT <webmasters-comment@gnu.org>
Cc: 24572@debbugs.gnu.org
Subject: bug#24572: [Comment] Re: bug#24572: [gnu.org #1151531] Emacs Manual Page missing?
Date: Fri, 30 Sep 2016 05:22:08 -0400	[thread overview]
Message-ID: <20160930092207.GY30569@gnu.org> (raw)
In-Reply-To: <rt-3.4.5-22412-1475226027-374.1151531-20-0@rt.gnu.org>

On Fri, Sep 30, 2016 at 05:00:28AM -0400, eliz via RT wrote:
> > 
> > > [nknight@siaras.com - Ven. Sep. 30 00:42:20 2016]:
> > > 
> > > Section 10.9 of the Emacs manual (on "Lax Search") seems to be missing
> > > as
> > > of Thu Sep 29 21:40:28 PDT 2016.
> > > 
> > > I retrieved it from the following URL at about Tue Sep 27 17:48:16
> > > 2016 PDT:
> > > 
> > > https://www.gnu.org/software/emacs/manual/html_node/emacs/Lax-
> > > Search.html#Lax-Search
> 
> The node "Lax Search" does exist in the manual, I see it in the Info
> formatted manual.  So this is some problem with how the manual was
> generated and/or uploaded to www.gnu.org/software/.

I guess it's a new file that hasn't been added to CVS.

> So it's not a bug in Emacs.

No, unless Emacs was used to commit the manual as whole.

Thank you!





  parent reply	other threads:[~2016-09-30  9:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <RT-Ticket-1151531@rt.gnu.org>
     [not found] ` <CACCQNLREXsSA-SRug-rJRVTk8GULfWdaw3uzO5n+YPGKA8gyUA@mail.gmail.com>
2016-09-30  8:06   ` bug#24572: [gnu.org #1151531] Emacs Manual Page missing? Therese Godefroy via RT
2016-09-30  9:00     ` Eli Zaretskii
     [not found]       ` <rt-3.4.5-22412-1475226027-374.1151531-20-0@rt.gnu.org>
2016-09-30  9:22         ` Ineiev [this message]
2016-10-03 12:13           ` bug#24572: [Comment] " Nicolas Petton

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

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

  git send-email \
    --in-reply-to=20160930092207.GY30569@gnu.org \
    --to=ineiev@gnu.org \
    --cc=24572@debbugs.gnu.org \
    --cc=webmasters-comment@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.