unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: dhruva <dhruvakm@gmail.com>
To: "David Kastrup" <dak@gnu.org>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Emacs build on Windows: Prerequisites
Date: Wed, 28 Feb 2007 19:01:52 +0530	[thread overview]
Message-ID: <e3f230850702280531r34d1c4b2ge5a93bdfd9abed5@mail.gmail.com> (raw)
In-Reply-To: <85k5y2l941.fsf@lola.goethe.zz>

On 2/28/07, David Kastrup <dak@gnu.org> wrote:
> dhruva <dhruvakm@gmail.com> writes:

> > This will make it easier for me to build.
>
> Will it make it easier for the developers to maintain, in particular
> synchronizing it with the builds on other platforms?  The developers
> of the Windows port will be more qualified to answer this question
> than I am, but I still want to point out that at least I find the
> phrasing of your request coming across as somewhat self-centred.  A

I apologize for conveying something that I did not mean. Just a
communication gap. IMHO, since Emacs is distributed in source form,
there will be lot of people trying to build it. Hence, I was hoping to
reduce the dependency and make it a little easier to be able to build
on windows. It was not an attempt to complain nor criticize the
current setup but a genuine approach to make it more self contained.

> progression of the "Why should...", "Why can't it..." kind comes
> across like a complaint doubting the sanity of the addressed people's
> choices.  Whether or not that was your intent, it probably could have

Not complaining for sure. 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.

with best regards,
dhruva

-- 
Dhruva Krishnamurthy
Contents reflect my personal views only!

  reply	other threads:[~2007-02-28 13:31 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 [this message]
2007-02-28 22:05     ` Jason Rumney
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

  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=e3f230850702280531r34d1c4b2ge5a93bdfd9abed5@mail.gmail.com \
    --to=dhruvakm@gmail.com \
    --cc=dak@gnu.org \
    --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 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).