From: Eli Zaretskii <eliz@gnu.org>
To: Hongyi Zhao <hongyi.zhao@gmail.com>
Cc: alexander.adolf@condition-alpha.com, Emacs-devel@gnu.org
Subject: Re: Development Emacs based on Emacs and magit.
Date: Thu, 09 Sep 2021 09:15:40 +0300 [thread overview]
Message-ID: <83fsuel1f7.fsf@gnu.org> (raw)
In-Reply-To: <CAGP6POJDG_i2RmXkyhyhVk_n27iWMXWOn1BK_ur_Y61XqNXEZg@mail.gmail.com> (message from Hongyi Zhao on Thu, 9 Sep 2021 07:11:41 +0800)
> From: Hongyi Zhao <hongyi.zhao@gmail.com>
> Date: Thu, 9 Sep 2021 07:11:41 +0800
> Cc: Alexander Adolf <alexander.adolf@condition-alpha.com>, Emacs-devel@gnu.org
>
> > This is not about you or me or any other power user of Emacs. This is
> > about occasional contributors to Emacs, who are accustomed to use the
> > PR workflow via Web forms. IMO it would be counter-productive to
> > request those contributors to install and use Magit, just to be able
> > to submit a change to us.
>
> Thank you for pointing this out. Considering that Emacs is patched so
> frequently, has it already implemented a complete
> workflow/module/macro/function to wrap the steps described here [1]
> with just several or one keystroke?
No, because we don't want to force anything on the contributor's
workflow. Developing a change is not a one-keystroke thing, it
requires writing the code, testing it, sending the patch, receiving
review comments, modifying the code accordingly, etc. etc. I don't
see how this could be done with a single keystroke, even in principle.
next prev parent reply other threads:[~2021-09-09 6:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 14:45 Development Emacs based on Emacs and magit Hongyi Zhao
2021-09-08 15:48 ` Alexander Adolf
2021-09-08 16:26 ` Eli Zaretskii
2021-09-08 23:11 ` Hongyi Zhao
2021-09-09 6:15 ` Eli Zaretskii [this message]
2021-09-09 11:19 ` André A. Gomes
2021-09-09 15:37 ` Alexander Adolf
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=83fsuel1f7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Emacs-devel@gnu.org \
--cc=alexander.adolf@condition-alpha.com \
--cc=hongyi.zhao@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).