From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>,
Stefan Kangas <stefankangas@gmail.com>
Cc: arash@gnu.org, 58248@debbugs.gnu.org
Subject: bug#58248: Transient online manual: Wrong header and broken link
Date: Sun, 02 Oct 2022 17:26:31 +0300 [thread overview]
Message-ID: <83r0zq1eug.fsf@gnu.org> (raw)
In-Reply-To: <871qrqcobf.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun, 02 Oct 2022 16:06:28 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: 58248@debbugs.gnu.org, "'Eli Zaretskii'" <eliz@gnu.org>
> Date: Sun, 02 Oct 2022 16:06:28 +0200
>
> Arash Esbati <arash@gnu.org> writes:
>
> > when I visit the following link:
> >
> > https://www.gnu.org/software/emacs/manual/transient.html
> >
> > I see this:
>
> It looks like it's been updated manually, and not completely
> successfully.
>
> Making the manuals hangs for me:
>
> [larsi@stories ~/src/emacs/28.2]$ ./admin/make-manuals
> Making manuals (slow)...
> Adding compressed html files...
> Making manual tarfiles...
> Doing emacs...
> ...created emacs-manual-29.0.50.tar
> Doing lispref...
> ...created emacs-lispref-29.0.50.tar
> Doing lispintro...
> ...created emacs-lispintro-29.0.50.tar
> Doing misc...
> ...created emacs-misc-29.0.50.tar
> Making refcards...
>
> I guess what should be done is run that successfully and then run
> admin/upload-manuals? Eli, can you have a look at that?
I think Stefan (CC'ed) prepared the manuals this time.
next prev parent reply other threads:[~2022-10-02 14:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-02 11:19 bug#58248: Transient online manual: Wrong header and broken link Arash Esbati
2022-10-02 14:06 ` Lars Ingebrigtsen
2022-10-02 14:26 ` Eli Zaretskii [this message]
2022-10-02 14:27 ` Stefan Kangas
2022-10-02 14:36 ` Lars Ingebrigtsen
2022-10-02 14:52 ` Stefan Kangas
2022-10-02 14:58 ` Lars Ingebrigtsen
2022-10-02 15:01 ` Lars Ingebrigtsen
2022-10-02 15:22 ` Stefan Kangas
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=83r0zq1eug.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58248@debbugs.gnu.org \
--cc=arash@gnu.org \
--cc=larsi@gnus.org \
--cc=stefankangas@gmail.com \
/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.