From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: cyd@stupidchicken.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Remove S_IFLNK
Date: Sat, 26 Feb 2011 14:36:19 -0800 [thread overview]
Message-ID: <4D698063.2000607@cs.ucla.edu> (raw)
In-Reply-To: <83vd06oetf.fsf@gnu.org>
On 02/26/2011 10:01 AM, Eli Zaretskii wrote:
> they are not important enough to justify such heavyweight changes
The changes are not heavyweight. In Emacs proper, the latest
proposal deletes 26 and inserts 9 lines, and I could easily reduce
that "9" to a "3" if you hadn't asked to retain a specially-worded
diagnostic for ENOSYS failure.
It's true that the change imports more stuff from gnulib, but
that's OK too. It's normal, and expected, and is good software
engineering practice, to move the porting complexity out of Emacs
proper and into the porting code.
> When you decide to merge it, please give me a day or two to add
> the stub functions for Windows and DOS, so that when you commit,
> these two ports will still build.
OK, I'll wait a couple of days before merging it.
next prev parent reply other threads:[~2011-02-26 22:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 19:37 windows build failure Sean Sieger
2011-02-21 19:40 ` Sean Sieger
2011-02-21 19:46 ` Christoph
2011-02-21 19:48 ` Paul Eggert
2011-02-21 20:21 ` Eli Zaretskii
2011-02-21 20:29 ` Lennart Borgman
2011-02-21 22:50 ` Sean Sieger
2011-02-21 20:37 ` Eli Zaretskii
2011-02-22 2:09 ` Paul Eggert
2011-02-22 8:57 ` Eli Zaretskii
2011-02-22 9:40 ` Paul Eggert
2011-02-22 10:49 ` Eli Zaretskii
2011-02-22 21:44 ` Paul Eggert
2011-02-23 9:47 ` Eli Zaretskii
2011-02-23 10:32 ` Eli Zaretskii
2011-02-25 21:28 ` Paul Eggert
2011-02-26 18:01 ` Remove S_IFLNK (was: windows build failure) Eli Zaretskii
2011-02-26 20:01 ` Remove S_IFLNK Stefan Monnier
2011-02-26 22:36 ` Paul Eggert [this message]
2011-02-27 19:54 ` 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=4D698063.2000607@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=cyd@stupidchicken.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.