From: Stephen Leake <stephen_leake@member.fsf.org>
Subject: Re: nt/makefile.w32-in
Date: Sun, 24 Dec 2006 14:53:23 -0500 [thread overview]
Message-ID: <ud5691364.fsf@member.fsf.org> (raw)
In-Reply-To: <E1GyIGp-0002zM-0G@fencepost.gnu.org> (Richard Stallman's message of "Sat, 23 Dec 2006 20:35:23 -0500")
Richard Stallman <rms@gnu.org> writes:
> 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.
>
> No, no, no! Explanations belong in comments in the code.
Ok, that makes sense.
In this case, the issue is whether nt/makefile-w32-in and similar
files should have DOS or Unix line endings.
There are no comments about line endings in the file.
Perhaps it should say:
# Using DOS line endings for Emacs 22. We've flipflopped on this
# several times; let's document why we make the next change.
--
-- Stephe
next prev parent reply other threads:[~2006-12-24 19:53 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 ` nt/makefile.w32-in Eli Zaretskii
2006-12-24 1:35 ` nt/makefile.w32-in Richard Stallman
2006-12-24 19:53 ` Stephen Leake [this message]
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
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=ud5691364.fsf@member.fsf.org \
--to=stephen_leake@member.fsf.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).