unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: Tramp changelog entries messes up lisp/ChangeLog
Date: Thu, 06 Feb 2003 14:49:52 +0100	[thread overview]
Message-ID: <84fzr1sem7.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: 5xptq67259.fsf@kfs2.cua.dk

storm@cua.dk (Kim F. Storm) writes:

> 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'm sorry.  Should I go back and summarize the ChangeLog entries and
consolidate them into a single entry?

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?  Or should there be just one entry?

In the past, I've tried to summarize the ChangeLog entries, but this
time I was too lazy to do that and somewhat in a hurry to just get
the new version out.  (But I still missed the XEmacs package.)  Sorry
about this.
-- 
A turnip curses Elvis

  parent reply	other threads:[~2003-02-06 13:49 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 [this message]
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
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=84fzr1sem7.fsf@lucy.is.informatik.uni-duisburg.de \
    --to=kai.grossjohann@uni-duisburg.de \
    /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).