all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman.073@student.lu.se>
Cc: Eli Zaretskii <eliz@gnu.org>,
	emacs-devel@gnu.org, Jason Rumney <jasonr@gnu.org>
Subject: Re: nt/makefile.w32-in
Date: Fri, 22 Dec 2006 00:56:31 +0100	[thread overview]
Message-ID: <458B1F2F.5090206@student.lu.se> (raw)
In-Reply-To: <f7ccd24b0612211545u79733a81w548fc277a882f246@mail.gmail.com>

Juanma Barranquero wrote:
> On 12/22/06, Lennart Borgman <lennart.borgman.073@student.lu.se> wrote:
>
>> If we assume the make ports people use does not care about line endings,
>> then yes. Otherwise no.
>
> I think we can safely assume something stronger: that relatively few
> people try to build Emacs on Windows (the only build environment where
> the [gn]make.defs issue is relevant), and the ones who do are usually
> able to gather the info they need to successfully compile Emacs,
> whether from a source tarball or from CVS. That's not to say we don't
> have to make things easy; but certainly doesn't seem an urgent issue
> right now.
>
> (This from yours truly, who twice spent a good deal of time wondering
> why nmake refused to work before thinking of checking line endings...)

I was going to write something similar, but my conclusion is different. 
What harm does it make to make the change now then? It will be in the 
release if we make it.

  reply	other threads:[~2006-12-21 23:56 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                   ` Lennart Borgman [this message]
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=458B1F2F.5090206@student.lu.se \
    --to=lennart.borgman.073@student.lu.se \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jasonr@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 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.