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: Mon, 19 Jan 2015 10:00:55 -0800 [thread overview]
Message-ID: <54BD4657.3010202@cs.ucla.edu> (raw)
In-Reply-To: <83y4oyycz8.fsf@gnu.org>
Eli Zaretskii wrote:
> Doing nothing means leaving the parts
> you side-stepped to bit-rot and generate bug reports,
Nothing is rotting here, as the code is working. No bug reports have been
generated because of this longstanding practice. As the benefits of the
proposed change to the practice do not appear to exceed the costs, I'd rather
leave things be.
> Leaving it to others to discover the places that were omitted, without
> any guidance as to how to identify them is too error-prone
No special guidance is needed, as the search heuristics are obvious. For
example, if the change involves replacing strcat with stpcpy, look at all uses
of strcat in the modules you're interested in.
next prev parent reply other threads:[~2015-01-19 18:00 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 [this message]
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=54BD4657.3010202@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.