all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Omitting Windows-specific parts from infrastructure changes
Date: Wed, 21 Jan 2015 21:08:20 +0100	[thread overview]
Message-ID: <87y4ovsxqj.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <54C00076.1020406@cs.ucla.edu> (Paul Eggert's message of "Wed, 21 Jan 2015 11:39:34 -0800")

Paul Eggert <eggert@cs.ucla.edu> writes:

> On 01/21/2015 09:55 AM, Eli Zaretskii wrote:
>
>> I could simply object to your changes that do a
>> partial job, or revert them.
>
> Wow, is this really a threat to block or revert changes to the Emacs
> mainline code, as leverage to force people to do unnecessary
> drudgework to help polish up the MS-Windows code?

I don't see a threat here.  When a change in master breaks functionality
for a number of people, the change is reverted as a rule in the projects
that I am an active member of.  Once the problems have been sorted out,
the change may be recommitted.

A half-finished change does not just affect the person who ends up
fixing the change but everybody else who is working on the platforms
broken by a change.  Not everyone is in a position to fix every change,
and there is no point in having a dozen people frantically working on
the same fix.

Emacs is developed with a distributed version control system so working
on private changes is perfectly possible without affecting the common
public repository.

Where a change requires involving multiple platform maintainers, it is
easily possible to first propose/provide the change in a branch where
the respective platform developers able to test or cater for a change
can prepare such changes without affecting the usability of the master
branch for other developers.

> This is starting to get ridiculous.

It struck me as ridiculous for quite longer than you it would seem, but
then I would guess for quite different reasons.

> Let's drop the discussion, as we're not making any progress (quite the
> reverse, I'm afraid).

While it does not appear that you've changed the stance of either of you
two in any way, at least others became aware of the issue and of your
inability to come to an agreement.  That makes it more likely that
others will try contributing to a resolution in case the problem
reappears.

But since resentment tends to be higher when people not directly
affected try effecting a change, that tends to have a worse chance for
deescalating the situation than if those directly affected can find a
way of cooperating themselves.

-- 
David Kastrup



  parent reply	other threads:[~2015-01-21 20:08 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 [this message]
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=87y4ovsxqj.fsf@fencepost.gnu.org \
    --to=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.