From: Eli Zaretskii <eliz@gnu.org>
Cc: lekktu@gmail.com, emacs-devel@gnu.org, jasonr@gnu.org
Subject: Re: nt/makefile.w32-in
Date: Sat, 23 Dec 2006 03:51:50 +0200 [thread overview]
Message-ID: <u4prnl6q1.fsf@gnu.org> (raw)
In-Reply-To: <uk60j5r0o.fsf@member.fsf.org> (message from Stephen Leake on Fri, 22 Dec 2006 20:40:07 -0500)
> Cc: lekktu@gmail.com, jasonr@gnu.org, emacs-devel@gnu.org
> From: Stephen Leake <stephen_leake@member.fsf.org>
> Date: Fri, 22 Dec 2006 20:40:07 -0500
>
> I don't have anything to add directly to this discussion, but it would
> help tremendously if people would put _explanations_ in the changelog,
> instead of just listing the changes.
ChangeLog files are not supposed to explain, just list the changes.
The explanations should be in the comments in the changed file itself.
next prev parent reply other threads:[~2006-12-23 1:51 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-20 23:56 nt/makefile.w32-in Eli Zaretskii
2006-12-21 0:03 ` nt/makefile.w32-in Juanma Barranquero
2006-12-21 11:37 ` nt/makefile.w32-in Jason Rumney
2006-12-21 12:00 ` nt/makefile.w32-in Juanma Barranquero
2006-12-21 21:02 ` nt/makefile.w32-in Eli Zaretskii
2006-12-21 21:18 ` nt/makefile.w32-in Lennart Borgman
2006-12-21 21:41 ` nt/makefile.w32-in Eli Zaretskii
2006-12-21 22:48 ` nt/makefile.w32-in Lennart Borgman
2006-12-21 23:16 ` nt/makefile.w32-in Jason Rumney
2006-12-21 23:35 ` nt/makefile.w32-in Lennart Borgman
2006-12-21 23:45 ` nt/makefile.w32-in Juanma Barranquero
2006-12-21 23:56 ` nt/makefile.w32-in Lennart Borgman
2006-12-22 0:19 ` nt/makefile.w32-in Juanma Barranquero
2006-12-22 2:01 ` nt/makefile.w32-in Lennart Borgman
2006-12-22 10:13 ` nt/makefile.w32-in Juanma Barranquero
2006-12-22 11:12 ` nt/makefile.w32-in Eli Zaretskii
2006-12-22 11:09 ` nt/makefile.w32-in Eli Zaretskii
2006-12-22 12:07 ` nt/makefile.w32-in Juanma Barranquero
2006-12-22 11:07 ` nt/makefile.w32-in Eli Zaretskii
2006-12-22 11:41 ` nt/makefile.w32-in Eli Zaretskii
2006-12-22 12:10 ` nt/makefile.w32-in Jason Rumney
2006-12-22 16:07 ` nt/makefile.w32-in Eli Zaretskii
2006-12-22 16:51 ` nt/makefile.w32-in Jason Rumney
2006-12-22 12:35 ` nt/makefile.w32-in Juanma Barranquero
2006-12-23 1:40 ` nt/makefile.w32-in Stephen Leake
2006-12-23 1:51 ` Eli Zaretskii [this message]
2006-12-24 1:35 ` nt/makefile.w32-in Richard Stallman
2006-12-24 19:53 ` nt/makefile.w32-in Stephen Leake
2006-12-25 16:53 ` nt/makefile.w32-in Richard Stallman
2006-12-27 13:42 ` nt/makefile.w32-in Eli Zaretskii
2006-12-22 23:38 ` nt/makefile.w32-in Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2006-12-20 23:56 nt/makefile.w32-in Eli Zaretskii
2006-12-22 11:34 nt/makefile.w32-in LENNART BORGMAN
2006-12-22 11:54 ` nt/makefile.w32-in Eli Zaretskii
2006-12-22 12:15 ` nt/makefile.w32-in Juanma Barranquero
2006-12-22 17:28 ` nt/makefile.w32-in Lennart Borgman
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=u4prnl6q1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jasonr@gnu.org \
--cc=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.