From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: David Kastrup <dak@gnu.org>, emacs-devel@gnu.org, eggert@cs.ucla.edu
Subject: Re: Omitting Windows-specific parts from infrastructure changes
Date: Thu, 22 Jan 2015 09:20:09 -0500 [thread overview]
Message-ID: <jwvr3umaoen.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83vbjzv5fe.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 22 Jan 2015 05:51:33 +0200")
I don't want to get into this discussion, but in case people wonder
where I stand, I fully agree with Eli's position below.
Stefan
> No, we are talking about making changes in infrastructure used by all
> platforms. Once someone decides to make such changes, making
> good-faith effort to do that in all parts of Emacs is part of the job.
> It could be done either by actually making those changes all over, or
> by asking platform maintainers to do the parts related to their
> platforms. In the latter case, the platform maintainers should have
> enough information about the proposed change to be able to do their
> parts without investing too much time and effort where the initiator
> can help them avoid that.
> For example, in the recently discussed changeset that uses CALLN for
> some C-level calls to Lisp APIs, the information that should be passed
> to platform maintainers is how to identify the offending calls. This
> information is clear to the person who initiated the change and it's
> possible to describe it in a sentence or two. I have hard time
> understanding how this kind of requirement could be described as
> impossible or hard to comply.
prev parent reply other threads:[~2015-01-22 14:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 9:54 Omitting Windows-specific parts from infrastructure changes Eli Zaretskii
2015-01-17 3:39 ` Paul Eggert
2015-01-17 8:34 ` Eli Zaretskii
2015-01-18 18:09 ` Paul Eggert
2015-01-18 18:23 ` Eli Zaretskii
2015-01-18 19:25 ` Paul Eggert
2015-01-18 19:50 ` Eli Zaretskii
2015-01-18 20:34 ` Paul Eggert
2015-01-19 16:03 ` Eli Zaretskii
2015-01-19 18:00 ` Paul Eggert
2015-01-19 18:32 ` Eli Zaretskii
2015-01-19 22:14 ` Paul Eggert
2015-01-20 16:32 ` Eli Zaretskii
2015-01-20 21:28 ` Paul Eggert
2015-01-21 15:48 ` Eli Zaretskii
2015-01-21 17:32 ` Paul Eggert
2015-01-21 17:55 ` Eli Zaretskii
2015-01-21 19:39 ` Paul Eggert
2015-01-21 20:07 ` Dmitry Gutov
2015-01-21 20:38 ` Eli Zaretskii
2015-01-21 20:08 ` David Kastrup
2015-01-21 20:49 ` Eli Zaretskii
2015-01-21 20:57 ` David Kastrup
2015-01-22 3:53 ` Eli Zaretskii
2015-01-21 20:30 ` Eli Zaretskii
2015-01-21 20:49 ` David Kastrup
2015-01-22 3:51 ` Eli Zaretskii
2015-01-22 14:20 ` Stefan Monnier [this message]
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=jwvr3umaoen.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=dak@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@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 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.