From: David Kastrup <dak@gnu.org>
Cc: karl@freefriends.org, emacs-devel@gnu.org
Subject: Re: makeinfo 4.7
Date: Mon, 28 Aug 2006 01:03:59 +0200 [thread overview]
Message-ID: <85mz9psrvk.fsf@lola.goethe.zz> (raw)
In-Reply-To: <E1GHTFy-0000sD-4E@fencepost.gnu.org> (Eli Zaretskii's message of "Sun, 27 Aug 2006 18:37:30 -0400")
Eli Zaretskii <eliz@gnu.org> writes:
>> Cc: emacs-devel@gnu.org, karl@freefriends.org
>> From: David Kastrup <dak@gnu.org>
>> Date: Mon, 28 Aug 2006 00:30:01 +0200
>>
>> > I thought the GNU project was about being able to modify the manual,
>> > not only use whatever is shipped with the tarballs.
>>
>> If you are modifying the manual, you can be expected to be using
>> development tools that are not from the stone age.
>
> If it is really necessary to ask them to upgrade, I agree. But this
> is not our case. Are you saying we should ask people to upgrade for
> no good reason at all?
>
>> That is nothing an inexperienced user would do.
>
> There's nothing in "make info" that requires any particular
> experience, IMO.
"make info" will not do anything in a released tarball unless you
touched the manual sources.
>> > On top of that, a large number of users who aren't developers are
>> > using the CVS code, where you must have Texinfo to produce the
>> > manual.
>>
>> Again, this is nothing an inexperienced user would do.
>
> I think you should check your facts. It is no longer true that only
> hackers use the CVS code.
Inexperienced users use CVS code somebody else compiled. Basically
all GNU/Linux distributions provide some emacs-snapshot package, and
there are several precompiled offers for MacOSX and Windows.
I don't see somebody juggling with CVS and compiling himself and so on
use a makeinfo from several years ago and being unable to upgrade.
It just does not make sense.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2006-08-27 23:03 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-25 21:54 makeinfo 4.7 Kim F. Storm
2006-08-25 23:03 ` Eli Zaretskii
2006-08-25 23:35 ` Kim F. Storm
2006-08-26 8:11 ` Alan Mackenzie
2006-08-26 12:15 ` Eli Zaretskii
2006-08-26 12:46 ` Eli Zaretskii
2006-08-26 14:23 ` Alan Mackenzie
2006-09-01 17:55 ` Eli Zaretskii
2006-08-26 12:22 ` Richard Stallman
2006-08-26 17:11 ` Karl Berry
2006-08-27 14:34 ` Richard Stallman
2006-08-27 16:16 ` Eli Zaretskii
2006-08-27 16:26 ` David Kastrup
2006-08-27 22:27 ` Eli Zaretskii
2006-08-27 22:30 ` David Kastrup
2006-08-27 22:37 ` Eli Zaretskii
2006-08-27 23:03 ` David Kastrup [this message]
2006-08-30 9:48 ` Eli Zaretskii
2006-08-30 9:52 ` David Kastrup
2006-08-28 8:20 ` Kim F. Storm
2006-08-29 16:06 ` Karl Berry
2006-08-29 16:49 ` Stefan Monnier
2006-08-30 11:27 ` Eli Zaretskii
2006-08-30 13:34 ` Kim F. Storm
2006-08-30 9:57 ` Eli Zaretskii
2006-08-30 11:20 ` Kim F. Storm
2006-08-30 22:59 ` Juri Linkov
2006-08-30 23:33 ` David Kastrup
2006-08-31 2:42 ` Miles Bader
2006-08-31 3:30 ` Eli Zaretskii
2006-08-31 23:35 ` Juri Linkov
2006-08-28 22:09 ` Richard Stallman
2006-08-30 10:44 ` Eli Zaretskii
2006-09-01 17:53 ` Eli Zaretskii
2006-08-28 15:14 ` Stefan Monnier
2006-08-30 10:32 ` 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=85mz9psrvk.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=karl@freefriends.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.