all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: lekktu@gmail.com, emacs-devel@gnu.org
Subject: Re: nt/makefile.w32-in
Date: Thu, 21 Dec 2006 23:02:04 +0200	[thread overview]
Message-ID: <upsadm08j.fsf@gnu.org> (raw)
In-Reply-To: <458A71F9.2050709@gnu.org> (message from Jason Rumney on Thu, 21 Dec 2006 11:37:29 +0000)

> Date: Thu, 21 Dec 2006 11:37:29 +0000
> From: Jason Rumney <jasonr@gnu.org>
> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
> 
> but those directories are not used by the Windows port, so there is no 
> reason for anyone to edit them on Windows (except for msdos, but I guess 
> either nothing has changed for a long time, or Eli checks out everything 
> with Unix line ends so hasn't seen the problem).

I always checkout with -kb (and that's the advice nt/INSTALL gives).

But the original question still stands: is there any reason not to
convert nt/makefile.w32-in to Unix EOLs?  Will something in the build
procedure break?

[...time passes...] Ah, I see this entry in nt/ChangeLog:

    2000-09-03  Andrew Innes  <andrewi@gnu.org>

	    * makefile.w32-in: Change to DOS line endings.

So I guess there _was_ a good reason for this, at least in the past,
and we better leave it that way, at least until after the release.

  parent reply	other threads:[~2006-12-21 21:02 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     ` Eli Zaretskii [this message]
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                     ` 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=upsadm08j.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@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.