From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Omitting Windows-specific parts from infrastructure changes
Date: Sun, 18 Jan 2015 12:34:01 -0800 [thread overview]
Message-ID: <54BC18B9.50202@cs.ucla.edu> (raw)
In-Reply-To: <837fwjzx5f.fsf@gnu.org>
Eli Zaretskii wrote:
> IOW, basically the request is to post a short note about things you
> know anyway. The only extra work is composing the message itself.
But as I mentioned, I don't know these things, as I don't look at the MS-Windows
code when I make changes like that. It's not reasonable to expect developers to
search all modules every time they make a change that could conceivably be
modified and/or adapted and/or adjusted to some other module. We already have
too much to do, and this extra bureaucracy's cost would outweigh its benefit.
next prev parent reply other threads:[~2015-01-18 20:34 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 [this message]
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
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=54BC18B9.50202@cs.ucla.edu \
--to=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.