all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Juanma Barranquero" <lekktu@gmail.com>
Subject: Re: lisp/ChangeLog
Date: Wed, 25 Oct 2006 13:30:32 +0200	[thread overview]
Message-ID: <f7ccd24b0610250430n75e9e59fje97dd9e6dba25dc3@mail.gmail.com> (raw)
In-Reply-To: <85k62o1z83.fsf@lola.goethe.zz>

On 10/25/06, David Kastrup <dak@gnu.org> wrote:

> I think lisp/ChangeLog should _at least_ contain all the stuff that
> happened since the last release.

AFAIK, that's *not* the case right now, if you're talking about relevant stuff.

I don't see what is so special in the changes between 21.4 (which was
a security-fix release, from a branch) and now. Unless I'm mistaken,
the last "new stuff" release was in 2001:

  2005-02-06  21.4
  2003-03-18  21.3
  2002-03-16  21.2
  2001-10-20  21.1

So, are you proposing to merge all changes from October 2001 on in
lisp/ChangeLog? :)

I'm only teasing, of course, but the fact is, ChangeLogs are mainly to
document changes (which works even if they're split) and as an aid to
us... and in that last case, if you need to search for changes to any
piece of code, you *already* have to search in more than one ChangeLog
file.

                    /L/e/k/t/u

  reply	other threads:[~2006-10-25 11:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-06  5:24 lisp/ChangeLog Nick Roberts
2005-10-07  3:03 ` lisp/ChangeLog Richard M. Stallman
2005-10-07  3:14   ` lisp/ChangeLog Nick Roberts
2005-10-07 19:08     ` lisp/ChangeLog Richard M. Stallman
2006-10-25 10:06       ` lisp/ChangeLog Juanma Barranquero
2006-10-25 10:11         ` lisp/ChangeLog David Kastrup
2006-10-25 11:30           ` Juanma Barranquero [this message]
2006-10-25 13:22           ` lisp/ChangeLog Kim F. Storm
2006-10-25 13:30             ` lisp/ChangeLog David Kastrup
2006-10-26  5:23         ` lisp/ChangeLog Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2005-07-28  2:46 lisp/ChangeLog Nick Roberts

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f7ccd24b0610250430n75e9e59fje97dd9e6dba25dc3@mail.gmail.com \
    --to=lekktu@gmail.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.