Re: /srv/bzr/emacs/trunk r102688: Minor clean up to silence somegcc warnings.

[Karl Fogel <kfogel@red-bean.com>]

"Drew Adams" <drew.adams@oracle.com> writes:
>And Emacs users often want to or sometimes need to understand the
>source code, and sometimes across versions.  And users who write Elisp
>code sometimes want to understand development changes within a given
>release cycle.
>
>Users deserve the source code, including its comments (which often reflect on
>implementation or design). Likewise its change logs (ditto).  Users should not
>need to access BZR or any other v-c interface to get access to the change-log
>info.  Delivering it as part of Emacs helps users.  Beyond delivering it with
>Emacs, making it available via http also helps - as in
>http://repo.or.cz/w/emacs.git/tree/HEAD:/lisp (or
>http://bazaar.launchpad.net/~vcs-imports/emacs/trunk/files/head%3A/lisp/, which
>doesn't work as well).
>
>Change-log info is meta-info about the code and its behavior, just like
>comments and doc and NEWS are.  Please keep it accessible to users
>locally, as part of their Emacs installation/delivery.

If "users should not need to access BZR" to get access to change-log
info, then that is not an argument for storing the ChangeLogs in BZR.

It is an argument for generating a user-friendly web page straight from
the version control logs (thus "making it available via http") and doing
something simliar when building a tarball distribution (thus "delivering
it with Emacs").

-Karl