unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
Cc: emacs-devel@gnu.org
Subject: Re: Tramp changelog entries messes up lisp/ChangeLog
Date: Thu, 6 Feb 2003 07:51:55 +0200 (IST)	[thread overview]
Message-ID: <Pine.SUN.3.91.1030206074757.6656A-100000@is> (raw)
In-Reply-To: <87hebi8hl4.fsf@emacswiki.org>


On Wed, 5 Feb 2003, Alex Schroeder wrote:

> storm@cua.dk (Kim F. Storm) writes:
> 
> > I would suggest creating a new lisp/net/tramp/ directory and move
> > the tramp*.el files there, and create a separate ChangeLog file there.
> > I suppose it will then make sense to move all of the tramp related
> > changelog entries from lisp/ChangeLog to lisp/net/tramp/ChangeLog.
> 
> But will you do this for every package that is maintained externally?

Probably not.  Which means maintainers of such packages should retag 
their entries with the check-in date.

Perhaps we should have a command to do that automatically on a region of 
a ChangeLog.  (Maybe there already is such a command, I didn't check.)

> And even if the order is wrong -- when exactly will that confuse us?

I frequently browse ChangeLog files to find out what was the sequence of 
changes, when some change breaks some feature.  So I think the dates 
should be in monotonous order, like they have been until now.

Also, it is confusing if the dates in CVS and in the change log are very 
different.

> I only ever use ChangeLog entries when I want to answer questions like
> "what where the recent changes related to file/variable/function foo"
> -- and for that, there need only be a very rough ordering of items.

Some changes interact, you know.

  reply	other threads:[~2003-02-06  5:51 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 [this message]
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
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=Pine.SUN.3.91.1030206074757.6656A-100000@is \
    --to=eliz@is.elta.co.il \
    --cc=emacs-devel@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.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).