unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: johns@fsf.org, emacs-devel@gnu.org
Subject: Re: Fwd: version vs edition numbers in Emacs manuals
Date: Fri, 15 Nov 2019 11:29:31 +0200	[thread overview]
Message-ID: <83tv7532tg.fsf@gnu.org> (raw)
In-Reply-To: <9f91d45c-d1c9-da2d-c4bf-20f22e4a59bb@cs.ucla.edu> (message from Paul Eggert on Thu, 14 Nov 2019 11:42:09 -0800)

> Cc: johns@fsf.org, emacs-devel@gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Thu, 14 Nov 2019 11:42:09 -0800
> 
> On 11/14/19 4:18 AM, Eli Zaretskii wrote:
> 
> > I didn't see John's response, not sure why.  Can someone forward it to
> > me?
> 
> Sure, here it is:

Thanks.

> > we should have a separate target in the Makefile, and we should maintain
> > the last printed edition in some separate file, because no one will
> > remember that otherwise.
> 
> A separate Makefile target would be fine, but the separate file should 
> be something that the FSF Press maintains.

How will that work in practice?  Isn't the printed version built by
using our Makefile's and our build infrastructure?  Then how can this
file be kept separate, and how will it be maintained to be available
when needed?

> The FSF Press is downstream from developers, they generate edition
> numbers at their convenience not developers', and they can and
> should be the ones who keep track of the edition numbers that they
> maintain.

Fine with me if that works.  But we must somehow make sure this
knowledge doesn't get lost.  Whoever prepares a manual for printing
should be aware that they need to do something that isn't already done
in the Emacs sources.  Maybe a simple README in those directories
could be the solution, e.g. if its name was indicative of its being a
necessary read when a manual is being prepared for printing.

Thoughts.

> > The fact that some manuals use EDITION while others use VERSION also
> > doesn't make this very clean, IMO.
> 
> Yes, that area could easily be made more systematic. For example, we 
> could systematically use just EDITION and DATE for all the FSF 
> Press-maintained info.

I'd like that, yes.



      reply	other threads:[~2019-11-15  9:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-02  0:35 version vs edition numbers in Emacs manuals Paul Eggert
2019-11-02  3:07 ` Jean-Christophe Helary
2019-11-02  7:59 ` Eli Zaretskii
2019-11-02 17:23   ` Paul Eggert
2019-11-02 18:26     ` Eli Zaretskii
2019-11-03  3:26   ` Richard Stallman
     [not found]     ` <aa8429f8-34d2-e998-2bc6-7f7707b11ded@cs.ucla.edu>
     [not found]       ` <87h83brvxg.fsf@wjsullivan.net>
     [not found]         ` <0a820310-d4ce-d9ab-32b0-5d22c00d2122@cs.ucla.edu>
     [not found]           ` <87sgmvozz9.fsf@wjsullivan.net>
2019-11-12 19:32             ` Fwd: " Paul Eggert
2019-11-14 12:18               ` Eli Zaretskii
2019-11-14 19:42                 ` Paul Eggert
2019-11-15  9:29                   ` Eli Zaretskii [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=83tv7532tg.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=johns@fsf.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).