From: "Drew Adams" <drew.adams@oracle.com>
To: "'Chong Yidong'" <cyd@stupidchicken.com>,
"'Stefan Monnier'" <monnier@iro.umontreal.ca>
Cc: 'Eli Zaretskii' <eliz@gnu.org>, emacs-devel@gnu.org
Subject: RE: /srv/bzr/emacs/trunk r102688: Minor clean up to silence somegcc warnings.
Date: Mon, 20 Dec 2010 07:31:27 -0800 [thread overview]
Message-ID: <C7AD80FDBFD3414EAA76D0270B5252AC@us.oracle.com> (raw)
In-Reply-To: <87ei9c34sr.fsf@stupidchicken.com>
> > In any case, the way forward is to stop using ChangeLog files.
>
> I still find the ChangeLog rather useful. Occasional extra
> verbiage in the bzr diffs and an extra minute's editing work
> when merging branches is not a large price to pay.
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.
next prev parent reply other threads:[~2010-12-20 15:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1PUCaG-00051g-NC@internal.in.savannah.gnu.org>
2010-12-19 11:41 ` /srv/bzr/emacs/trunk r102688: Minor clean up to silence some gcc warnings Romain Francoise
2010-12-19 13:59 ` Stefan Monnier
2010-12-19 15:01 ` Eli Zaretskii
2010-12-20 2:53 ` Stefan Monnier
2010-12-20 8:03 ` Štěpán Němec
2010-12-20 14:04 ` Stefan Monnier
2010-12-20 14:19 ` Chong Yidong
2010-12-20 15:31 ` Drew Adams [this message]
2010-12-20 16:51 ` /srv/bzr/emacs/trunk r102688: Minor clean up to silence somegcc warnings Karl Fogel
2010-12-20 17:18 ` Drew Adams
2010-12-20 18:05 ` Stefan Monnier
2010-12-20 18:08 ` /srv/bzr/emacs/trunk r102688: Minor clean up to silence some gcc warnings Stefan Monnier
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=C7AD80FDBFD3414EAA76D0270B5252AC@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=cyd@stupidchicken.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).