all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: bob@rattlesnake.com, emacs-devel@gnu.org, miles@gnu.org
Subject: Re: ChangeLog?
Date: Thu, 03 Mar 2005 15:57:44 -0500	[thread overview]
Message-ID: <E1D6xOC-0008IU-8L@fencepost.gnu.org> (raw)
In-Reply-To: <fc339e4a05030219201c4c5fcd@mail.gmail.com> (message from Miles Bader on Thu, 3 Mar 2005 12:20:00 +0900)

      From his reply, I gather
    than the documentation contradicts this position.

No, it doesn't.  That was a misunderstanding.

The Emacs manual describes multiple approaches for maintaining a
project.  Each project, however, has its own specific policies.  In
Emacs, the approach we use is that all changes are listed in
ChangeLog.

Bob, would you please put your change in ChangeLog?

  reply	other threads:[~2005-03-03 20:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <61k6osjqsz.fsf@fencepost.gnu.org>
     [not found] ` <m1D5t7c-0004QmC@rattlesnake.com>
     [not found]   ` <fc339e4a05022814485fe422fb@mail.gmail.com>
2005-03-01 13:29     ` ChangeLog? Robert J. Chassell
2005-03-01 14:12       ` ChangeLog? Stefan Monnier
2005-03-01 15:06         ` ChangeLog? Kim F. Storm
2005-03-01 16:11           ` ChangeLog? Stefan Monnier
2005-03-03  2:27       ` ChangeLog? Richard Stallman
2005-03-03  3:20         ` ChangeLog? Miles Bader
2005-03-03 20:57           ` Richard Stallman [this message]
2005-03-04  0:41             ` ChangeLog? Robert J. Chassell
2005-03-04  0:53               ` ChangeLog? Luc Teirlinck
2005-03-04  1:35               ` ChangeLog? Miles Bader
2005-03-04 13:42                 ` ChangeLog? Robert J. Chassell
2005-03-04  1:49               ` ChangeLog? Nick Roberts
2005-03-04 23:46                 ` ChangeLog? Richard Stallman
2005-03-04 23:46               ` ChangeLog? 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1D6xOC-0008IU-8L@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=bob@rattlesnake.com \
    --cc=emacs-devel@gnu.org \
    --cc=miles@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.