all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jason Rumney <jasonr@gnu.org>
To: dhruva <dhruvakm@gmail.com>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Emacs build on Windows: Prerequisites
Date: Wed, 28 Feb 2007 22:05:41 +0000	[thread overview]
Message-ID: <45E5FCB5.5050104@gnu.org> (raw)
In-Reply-To: <e3f230850702280531r34d1c4b2ge5a93bdfd9abed5@mail.gmail.com>

dhruva wrote:
> Before I start modifying the build files, I
> wanted to know if there was a reason that I had completely missed out.
> I just wanted to avoid spending time on a topic which was already
> visited by other developers.
>
There are a couple of paragraphs of commentary in nt/gmake.defs about 
why past maintainers chose to require cp and rm to build Emacs rather 
than use the Windows native del and copy commands.

  reply	other threads:[~2007-02-28 22:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-28 12:58 Emacs build on Windows: Prerequisites dhruva
2007-02-28 13:11 ` David Kastrup
2007-02-28 13:31   ` dhruva
2007-02-28 22:05     ` Jason Rumney [this message]
2007-03-01  4:17       ` dhruva
2007-03-01 10:44         ` Lennart Borgman (gmail)
2007-03-02 14:28         ` Vinicius Jose Latorre
2007-03-02 14:57           ` Lennart Borgman (gmail)
2007-03-02 15:20             ` Vinicius Jose Latorre
2007-03-02 15:33               ` Lennart Borgman (gmail)
2007-03-02 19:41                 ` Vinicius Jose Latorre
2007-03-02 20:10                   ` Lennart Borgman (gmail)
2007-03-02 20:51                     ` Vinicius Jose Latorre
2007-03-03 10:33                     ` Eli Zaretskii
2007-03-03 13:54                       ` Lennart Borgman (gmail)
2007-03-01  4:17       ` Eli Zaretskii
2007-02-28 16:55 ` Stephen J. Turnbull
2007-02-28 20:25   ` Eli Zaretskii
2007-02-28 20:18 ` Eli Zaretskii

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=45E5FCB5.5050104@gnu.org \
    --to=jasonr@gnu.org \
    --cc=dhruvakm@gmail.com \
    --cc=emacs-devel@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.