unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: "Kim F. Storm" <storm@cua.dk>
Subject: Re: Tramp changelog entries messes up lisp/ChangeLog
Date: Fri, 07 Feb 2003 18:10:07 -0500	[thread overview]
Message-ID: <E18hHdH-0003Hn-00@fencepost.gnu.org> (raw)
In-Reply-To: <5xptq67259.fsf@kfs2.cua.dk> (storm@cua.dk)

    I noticed that Kai (again) has included a big section of another
    ChangeLog file (for Tramp) into lisp/ChangeLog maintaining the dates
    of the original changelog.  I don't object to keeping those dates, but
    it completely messes up the sequence of entries in the ChangeLog file,
    as illustrated below.

When merging in changes that were made on various dates, the proper
thing to do is to combine and condense the change log entries and
enter them under a single date, which is the date that you installed
all the changes.

Kai, could you do that?

    I'd like to credit Michael with things he has done -- so should I
    make two ChangeLog entries out of this, one for Michael and one for
    me?

That is a good way to do it.

  parent reply	other threads:[~2003-02-07 23:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-05 23:12 Tramp changelog entries messes up lisp/ChangeLog Kim F. Storm
2003-02-05 22:53 ` Alex Schroeder
2003-02-06  5:51   ` Eli Zaretskii
2003-02-06 13:49 ` Kai Großjohann
2003-02-06 19:15   ` Eli Zaretskii
2003-02-07 16:06     ` Kai Großjohann
2003-02-07 17:14       ` Eli Zaretskii
2003-02-07 18:37         ` Kai Großjohann
2003-02-09 12:39       ` Richard Stallman
2003-02-07 23:10 ` Richard Stallman [this message]
2003-02-08  9:44   ` Eli Zaretskii
2003-02-10 10:34     ` Richard Stallman
2003-02-11 17:31       ` Kai Großjohann
2003-02-09 10:48   ` Kai Großjohann
2003-02-10 10:43     ` Andreas Schwab
2003-02-10 10:59       ` Kai Großjohann
2003-02-09 14:44   ` Kai Großjohann

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=E18hHdH-0003Hn-00@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=storm@cua.dk \
    /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).