From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Omitting Windows-specific parts from infrastructure changes
Date: Tue, 20 Jan 2015 18:32:48 +0200 [thread overview]
Message-ID: <833875xvin.fsf@gnu.org> (raw)
In-Reply-To: <54BD81C4.1070109@cs.ucla.edu>
> Date: Mon, 19 Jan 2015 14:14:28 -0800
> From: Paul Eggert <eggert@cs.ucla.edu>
> CC: emacs-devel@gnu.org
>
> Eli Zaretskii wrote:
> It is working because I cleaned it up. It didn't work before that
>
> No, the code already worked for the patches we're talking about, e.g., replacing strcat with stpcpy. And it still works, in the places where the MS-Windows code still uses strcat instead of stpcpy.
Beg your pardon, but how do you know this? Since you said you don't
look into the Windows modules and don't understand their code, you
cannot possibly know whether it works/worked or not.
> The costs are minuscule: just a short notice posted here.
>
> The costs would be more than that, as I'd need to examine code that I don't look at now
You already said you didn't want to do that, and I already said you
don't have to. So this is not required.
> and I'd have to save notes about the examination somewhere, and keep track of these notes during the time period between searching and installing the fix, which is often weeks.
Not required: just post those notes once when you first do the
examination, and don't bother updating them, if that's a burden.
> This would add nontrivial bureaucracy to the maintenance of mainline code, with only a trivial benefit to non-mainline maintenance.
I assure you, the benefit is not trivial for me. If it were, I
wouldn't have bothered starting all this uneasy discussion.
> It's not worth it.
It is worth it for me. Please help me maintain the parts of Emacs in
which you have no interest. Keeping those parts in good shape is a
prerequisite for my participation in the project, so it is of utmost
importance to me, if not to you. (I think it's also of importance to
the project as a whole, but we seem to have quite different views of
the project's good, so you'll probably disagree. However, I hope
others will agree with me.)
TIA
next prev parent reply other threads:[~2015-01-20 16:32 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 [this message]
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=833875xvin.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--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.