From: John Wiegley <jwiegley@gmail.com>
To: emacs-orgmode Mode <emacs-orgmode@gnu.org>
Subject: A request: Moving away from ChangeLog
Date: Fri, 21 May 2010 05:06:04 -0400 [thread overview]
Message-ID: <2151275B-C80E-4B40-9022-8C9054020163@gmail.com> (raw)
The Emacs ChangeLog is a file which predates the existence of freely available, project-wide version control. It was a way to see, in one place, the stream of changes occurring in a project -- something which RCS could not do for you.
However, in this modern era of project-wide, atomic commits, the ChangeLog is not only an archaism, but is a continuous source of merge conflicts. For example, when I reverted Russell's latest change -- a one-liner that was minor in the extreme -- I had to do with a merge conflict in lisp/ChangeLog.
With a system like Git, and properly written commits, you can produce a ChangeLog at any time with "git log". You even see a ChangeLog for just one file, or a directory with "git log --follow PATH". This completes supersedes any need for a ChangeLog file, and has led me to abandon the use of ChangeLogs in all the projects I maintain.
I would request we do so for Org-mode as well, unless there is some compelling reason to keep this file.
John
next reply other threads:[~2010-05-21 9:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 9:06 John Wiegley [this message]
2010-05-21 9:41 ` A request: Moving away from ChangeLog John Wiegley
2010-05-21 12:15 ` Carsten Dominik
2010-05-21 12:50 ` John Wiegley
2010-05-21 13:47 ` Tassilo Horn
2010-05-21 15:06 ` John Wiegley
2010-05-21 15:39 ` Bernt Hansen
2010-05-21 15:46 ` John Wiegley
2010-05-21 16:01 ` Bernt Hansen
2010-05-21 16:32 ` Eric Schulte
2010-05-21 15:53 ` Carsten Dominik
2010-05-21 15:58 ` John Wiegley
2010-05-21 14:32 ` Carsten Dominik
2010-05-21 15:08 ` John Wiegley
2010-05-21 15:33 ` John Wiegley
2010-05-21 13:01 ` Ben Finney
2010-05-21 14:21 ` Carsten Dominik
2010-05-21 21:10 ` Christian Egli
2010-05-21 21:17 ` Julien Danjou
2010-06-01 14:58 ` Carsten Dominik
2010-06-02 7:44 ` Christian Egli
2010-06-02 9:32 ` Carsten Dominik
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2151275B-C80E-4B40-9022-8C9054020163@gmail.com \
--to=jwiegley@gmail.com \
--cc=emacs-orgmode@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/org-mode.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).