From: Eli Zaretskii <eliz@gnu.org>
To: David Kastrup <dak@gnu.org>
Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org
Subject: Re: Omitting Windows-specific parts from infrastructure changes
Date: Thu, 22 Jan 2015 05:53:20 +0200 [thread overview]
Message-ID: <83twzjv5cf.fsf@gnu.org> (raw)
In-Reply-To: <87a91bhmwf.fsf@fencepost.gnu.org>
> From: David Kastrup <dak@gnu.org>
> Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org
> Date: Wed, 21 Jan 2015 21:57:52 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: David Kastrup <dak@gnu.org>
> >> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
> >> Date: Wed, 21 Jan 2015 21:08:20 +0100
> >>
> >> 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.
> >
> > That's certainly a possibility. But it, too, assumes some minimal
> > level of cooperation between the platform maintainers. At the very
> > least, the idea and perhaps also the details of the change should be
> > published. It makes no sense to ask others to guess how to find which
> > places on their platforms need change from large diffs.
>
> I disagree here since those others will know the way around their
> platform code better than someone catering for a different platform.
Once the information about what should be changed is given, yes. And
that is all that was requested.
> I would not myself go pointing out which stuff should be changed in the
> Windows code in order to parallel some GNU/Linux specific code changes
> I submit.
No one requested that.
> But that does not mean that a contributor should refrain from describing
> what he had to do on _his_ platform (with a high-level description
> rather than one tied into the platform-specific code) to accommodate the
> changes, and what functionality will likely be affected similarly on
> other platforms.
Exactly, this is the only request.
next prev parent reply other threads:[~2015-01-22 3:53 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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83twzjv5cf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dak@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).