From: dick.r.chiang@gmail.com
To: Philippe Vaucher <philippe.vaucher@gmail.com>
Cc: Mario Lang <mlang@delysid.org>, Jack Hill <jackhill@jackhill.us>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: ELPA: where is chess developed?
Date: Tue, 24 Mar 2020 07:38:24 -0400 [thread overview]
Message-ID: <87369yc79r.fsf@dick> (raw)
In-Reply-To: <CAGK7Mr7307+6bBGw-Hw+LMdeR0TWG+a1zFVVX1sj=jS-U7+uYw@mail.gmail.com> (Philippe Vaucher's message of "Tue, 24 Mar 2020 09:10:45 +0100")
> Just curious, can you elaborate why the ability to push gives you a tight
> feedback loop?
Notice how belabored the email-patch mechanism is for prospective
contributors without push access. Nature of the beast I'm afraid... there's
always at least one niggling fixup for the smallest patch submission, and for a
50-commit-behind-50-commit-ahead merge, there's going to be order of 10
fixups. The verbal back-and-forth required is prohibitively costly for a
largely inactive repo like emacs-chess.
The web-based "pull request" mechanism is much more sane than iterating emails
as it's always clear which of the author's iterations is latest, but that's a
separate issue.
next prev parent reply other threads:[~2020-03-24 11:38 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-22 22:35 ELPA: where is chess developed? Jack Hill
2020-03-23 4:26 ` John Wiegley
2020-03-23 13:50 ` dick.r.chiang
2020-03-23 14:27 ` Mario Lang
2020-03-23 15:12 ` dick.r.chiang
2020-03-24 8:10 ` Philippe Vaucher
2020-03-24 11:38 ` dick.r.chiang [this message]
2020-03-24 11:54 ` Philippe Vaucher
2020-03-24 14:12 ` Stefan Monnier
2020-03-24 14:41 ` Stefan Monnier
2020-03-27 2:59 ` pull requests Richard Stallman
2020-03-27 3:49 ` Stefan Monnier
2020-03-28 2:45 ` Richard Stallman
2020-03-28 3:03 ` Stefan Monnier
2020-03-27 7:54 ` Eli Zaretskii
2020-03-27 13:00 ` Clément Pit-Claudel
2020-03-27 13:30 ` Eli Zaretskii
2020-03-27 14:37 ` Clément Pit-Claudel
2020-03-27 15:21 ` Eli Zaretskii
2020-03-27 15:41 ` Dmitry Gutov
2020-03-27 19:16 ` Eli Zaretskii
2020-03-27 19:24 ` Dmitry Gutov
2020-03-27 19:34 ` 조성빈
2020-03-27 19:28 ` Eli Zaretskii
2020-03-27 20:39 ` Dmitry Gutov
2020-03-28 2:46 ` Richard Stallman
2020-03-28 17:14 ` Dmitry Gutov
2020-03-30 3:38 ` Richard Stallman
2020-03-30 4:09 ` Stefan Monnier
2020-03-30 5:58 ` Eli Zaretskii
2020-03-30 12:03 ` Dmitry Gutov
2020-03-30 12:55 ` Yuri Khan
2020-03-30 13:12 ` Eli Zaretskii
2020-03-30 13:50 ` Dmitry Gutov
2020-03-30 14:12 ` Eli Zaretskii
2020-03-30 14:34 ` Dmitry Gutov
2020-03-30 15:36 ` Eli Zaretskii
2020-03-30 15:50 ` Dmitry Gutov
2020-03-30 16:09 ` Eli Zaretskii
2020-03-30 17:06 ` Dmitry Gutov
2020-03-30 17:13 ` Eli Zaretskii
2020-04-02 2:39 ` Richard Stallman
2020-04-17 3:54 ` Dmitry Gutov
2020-03-30 13:43 ` Stefan Monnier
2020-03-30 16:59 ` Dmitry Gutov
2020-03-30 17:20 ` Stefan Monnier
2020-03-30 17:28 ` Dmitry Gutov
2020-03-30 8:25 ` 조성빈
2020-03-30 11:51 ` Dmitry Gutov
2020-03-30 13:04 ` Eli Zaretskii
2020-03-30 17:49 ` Dmitry Gutov
2020-03-27 16:39 ` Clément Pit-Claudel
2020-03-27 19:21 ` Eli Zaretskii
2020-03-27 14:05 ` Stefan Monnier
2020-03-28 2:46 ` Richard Stallman
2020-03-23 15:58 ` ELPA: where is chess developed? Stefan Monnier
2020-03-23 14:25 ` Mario Lang
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=87369yc79r.fsf@dick \
--to=dick.r.chiang@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jackhill@jackhill.us \
--cc=mlang@delysid.org \
--cc=philippe.vaucher@gmail.com \
/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).