unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex Schroeder <alex@emacswiki.org>
Cc: emacs-devel@gnu.org
Subject: Re: Tramp changelog entries messes up lisp/ChangeLog
Date: Wed, 05 Feb 2003 23:53:43 +0100	[thread overview]
Message-ID: <87hebi8hl4.fsf@emacswiki.org> (raw)
In-Reply-To: <5xptq67259.fsf@kfs2.cua.dk> (storm@cua.dk's message of "06 Feb 2003 00:12:34 +0100")

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?
And even if the order is wrong -- when exactly will that confuse us?
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.
Essentially, changes for every file, every variable, and every
function should be more or less chronological, but not the entries by
themselves.  Let me illustrate.

This is OK, because all A changes are ordered, and all B changes are
ordered:

2003-02-03  changes B
2003-02-02  changes B
 * time warp *
2003-02-05  changes A
2003-02-04  changes A
2003-02-01  changes B

This is not OK, because searching backwards for B will yield confusing
results.  But even then, if there are no unreasonable jumps in the
order of changes to B, I would not mind:

2003-02-03  changes B
2003-02-02  changes C
 * time warp *
2003-02-05  changes B
2003-02-04  changes A
2003-02-01  changes B

In this case, two different people changed B after 2003-02-01, and
perhaps one of them even had to resolve conflicts, and that would
explain the time line.  But as I said -- I will often use C-s to
search for some item foo, and jump up and down in the ChangeLog.  So
as long as it is just aproximately correct, I don't mind time warps.

Alex.

  reply	other threads:[~2003-02-05 22:53 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 [this message]
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
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=87hebi8hl4.fsf@emacswiki.org \
    --to=alex@emacswiki.org \
    --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).