unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Robert J. Chassell" <bob@rattlesnake.com>
Subject: Re: ChangeLog?
Date: Fri, 4 Mar 2005 00:41:39 +0000 (UTC)	[thread overview]
Message-ID: <m1D70st-0004R9C@rattlesnake.com> (raw)
In-Reply-To: <E1D6xOC-0008IU-8L@fencepost.gnu.org> (message from Richard Stallman on Thu, 03 Mar 2005 15:57:44 -0500)

        I gather the documentation contradicts this position.

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

    In Emacs, the approach we use is that all changes are listed in
    ChangeLog.

Which ChangeLog?  The Emacs CVS offers two ChangeLogs and in
    (emacs)Types of Log File
the Emacs manual says

    When you use version control, you can use just the per-file log if
    you wish, or you can use both kinds of logs.  ...

So I originally used the smaller, per-file ChangeLog.  Miles persuaded
me to add a comment to the larger ChangeLog, which I did.

Shall I change the documentation as I suggested to:

        emacs/man/files.texi   
        Types of Log File

    When you use a version control system that provides a per-file
    log, you should use @strong{both} the the per-file log and the
    more general @file{ChangeLog}.  This is because it is inconvenient
    or impossible for someone using a different version control system
    to access another version control system's per-file log.  This
    policy is different from the past, when you recorded small changes
    in the per-file log only.

    Typically you want to write just one entry for each change.  You
    can write the entry in @file{ChangeLog}, using the @kbd{C-x 4 a}
    command (@pxref{Change Log}), and then copy it to the log buffer
    when you check in the change.  Or you can write the entry in the
    log buffer while checking in the change, using the @kbd{C-x v v}
    command, and later use the @kbd{C-x v a} command to copy it to the
    more general @file{ChangeLog} (@pxref{Change Logs and VC}).

My hunch is that the current documentation is different than you
thought and that the changed documentation says what you mean.

-- 
    Robert J. Chassell                         
    bob@rattlesnake.com                         GnuPG Key ID: 004B4AC8
    http://www.rattlesnake.com                  http://www.teak.cc

  reply	other threads:[~2005-03-04  0:41 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           ` ChangeLog? Richard Stallman
2005-03-04  0:41             ` Robert J. Chassell [this message]
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

  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=m1D70st-0004R9C@rattlesnake.com \
    --to=bob@rattlesnake.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).