From: Karl Fogel <kfogel@red-bean.com>
To: emacs-devel@gnu.org
Subject: ChangeLog policy for same-day changes to a file?
Date: Wed, 02 Jan 2008 00:58:15 -0800 [thread overview]
Message-ID: <87hchwr4d4.fsf@red-bean.com> (raw)
Notice the multiple appearances of "doc-view.el" in this single entry
from lisp/ChangeLog:
2007-12-26 Tassilo Horn <tassilo@member.fsf.org>
* image-mode.el (image-bookmark-make-cell, image-bookmark-jump):
New functions.
(image-mode): Set bookmark-make-cell-function appropriately.
* doc-view.el (doc-view-bookmark-jump): Correct misspelled arg name.
* bookmark.el (bookmark-make-cell-function): New variable.
(bookmark-make): Call bookmark-make-cell-function's function
instead of bookmark-make-cell.
(bookmark-get-handler, bookmark-jump-internal): New functions.
(bookmark-jump, bookmark-jump-other-window, bookmark-insert)
(bookmark-bmenu-2-window, bookmark-bmenu-other-window):
Use bookmark-jump-internal.
(bookmark-make-cell-for-text-file): Renamed from bookmark-make-cell.
* doc-view.el (doc-view-bookmark-make-cell)
(doc-view-bookmark-jump): New functions.
(doc-view-mode): Set bookmark-make-cell-function buffer-locally.
Obviously, they represent separate CVS commits to doc-view.el, but on
the same day, so Tassilo put them into the same ChangeLog entry. The
result is counterintuitive, but I'm not sure what else he should do.
Create a separate ChangeLog entry with the same date? Do we have a
policy for how to handle this?
(I have little experience with this issue, because no other project I
work on manually maintains a ChangeLog file in addition to the log
messages stored by the version control system.)
-Karl
next reply other threads:[~2008-01-02 8:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-02 8:58 Karl Fogel [this message]
2008-01-02 7:06 ` ChangeLog policy for same-day changes to a file? Miles Bader
2008-01-02 9:39 ` Karl Fogel
2008-01-02 7:46 ` Miles Bader
2008-01-03 9:50 ` Richard Stallman
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=87hchwr4d4.fsf@red-bean.com \
--to=kfogel@red-bean.com \
--cc=emacs-devel@gnu.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).