From: Sebastian Urban <mrsebastianurban@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 41009@debbugs.gnu.org
Subject: bug#41009: Add release date to the title page of Emacs manual (PDF)
Date: Sun, 3 May 2020 23:38:31 +0200 [thread overview]
Message-ID: <05ef06ab-cd27-11ee-fedf-837ccef887f3@gmail.com> (raw)
In-Reply-To: <4uy2q8ly7b.fsf@fencepost.gnu.org>
> If you mean when the FSF produce a published version, only they
> could add that date, and it would not be known at the time of the
> associated Emacs release. If you mean when the associated Emacs was
> released, then I don't see why that date should be added, but it
> could eg be extracted from etc/HISTORY, with some small trouble.
I thought that it'll be simpler, merely a question of whether to put
it or not to put it.
I'm guessing that release of docs depend on release of Emacs itself,
but because I don't know anything about how you are releasing them, in
it's difficult for me to define "release date". So, I would have to
know the sequence of the release process to pick a good place in time,
which, in my opinion of course, should be the release date.
I'm guessing that on day N, Emacs is packaged (tar.gz) and uploaded
to: http://ftp.gnu.org/gnu/emacs/
But then, is documentation (Info, PDF, HTML, sources package) also
build on the same day and uploaded to:
https://www.gnu.org/software/emacs/manual/emacs.html
Or maybe documentation is uploaded few days after?
And then do they (docs) stay the same until next Emacs release, or are
they refreshed (corrected style, some minor errors/typos)?
S. U.
next prev parent reply other threads:[~2020-05-03 21:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 20:19 bug#41009: Add release date to the title page of Emacs manual (PDF) Sebastian Urban
2020-05-02 6:05 ` Eli Zaretskii
2020-05-02 19:52 ` Sebastian Urban
2020-05-02 20:05 ` Stefan Kangas
2020-05-03 17:34 ` Glenn Morris
2020-05-03 21:38 ` Sebastian Urban [this message]
2020-05-04 3:15 ` Richard Stallman
2020-05-03 22:13 ` Stefan Kangas
2020-05-05 2:49 ` Richard Stallman
2020-05-28 15:38 ` Sebastian Urban
2020-05-28 16:12 ` Eli Zaretskii
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=05ef06ab-cd27-11ee-fedf-837ccef887f3@gmail.com \
--to=mrsebastianurban@gmail.com \
--cc=41009@debbugs.gnu.org \
--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 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.