From: "Drew Adams" <drew.adams@oracle.com>
To: "'Štepán Nemec'" <stepnem@gmail.com>
Cc: 7367@debbugs.gnu.org
Subject: bug#7367: 24.0.50; change logs in source code
Date: Thu, 11 Nov 2010 09:03:46 -0800 [thread overview]
Message-ID: <5DC618A15B0C46E4A3907092DCEAFA7E@us.oracle.com> (raw)
In-Reply-To: <87oc9vg6c8.fsf@gmail.com>
Hey, why not give users only Internet links for the source code too while you're
at it? Why bother to give them the source code for local use? Better yet, just
tell them to search the Internet for it.
Change log info, like any info, can be of variable quality/utility. It is info
about the source code, just like comments (and diffs) are, and as such it can be
useful to at least some users. Just like comments, it can inform you about
implementation and design logic - the intentions behind what is there currently.
The point is not that all change logs provide great info; the point is that
users deserve to have the info locally, whatever it is and however useful it
might be. They should not be shoved off to search the Internet.
next prev parent reply other threads:[~2010-11-11 17:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 20:46 bug#7367: 24.0.50; change logs in source code Drew Adams
2010-11-11 16:42 ` Štěpán Němec
2010-11-11 17:03 ` Drew Adams [this message]
2011-07-09 19:00 ` Glenn Morris
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=5DC618A15B0C46E4A3907092DCEAFA7E@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=7367@debbugs.gnu.org \
--cc=stepnem@gmail.com \
/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).