From: Eli Zaretskii <eliz@gnu.org>
To: Tim Cross <theophilusx@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Why not set Emacs development workflow based on the popular git forges (GitHub, Bitbucket, Gitlab, ect)?
Date: Thu, 09 Sep 2021 09:12:38 +0300 [thread overview]
Message-ID: <83h7eul1k9.fsf@gnu.org> (raw)
In-Reply-To: <87a6kmfz8n.fsf@gmail.com> (message from Tim Cross on Thu, 09 Sep 2021 08:49:11 +1000)
> From: Tim Cross <theophilusx@gmail.com>
> Date: Thu, 09 Sep 2021 08:49:11 +1000
>
> To be proposing a whole new workflow just to facilitate the first step
> i.e. contributing a patch, seems to be a little too much and feels like
> it cold run the risk of throwing the baby out with the bathwater.
This is something for the active developers to decide. And we have
made that decision: we are willing to switch to a platform which makes
it easier for occasional contributors to work with us. We are just
looking for a platform that will fit our minimal requirements, which
is likely to require some changes in even the best of the platforms.
So let's not keep arguing about whether this kind of change in
supported workflows is justified: we already made the decision, and I
see no reason to reverse it, not yet anyway.
next prev parent reply other threads:[~2021-09-09 6:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-04 6:55 Why not set Emacs development workflow based on the popular git forges (GitHub, Bitbucket, Gitlab, ect)? Hongyi Zhao
2021-09-04 7:13 ` tomas
2021-09-04 11:24 ` Po Lu
2021-09-04 11:34 ` tomas
2021-09-04 11:38 ` Po Lu
2021-09-04 12:11 ` tomas
2021-09-04 12:51 ` Po Lu
2021-09-04 12:50 ` Hongyi Zhao
2021-09-04 13:28 ` Po Lu
2021-09-05 0:56 ` Hongyi Zhao
2021-09-05 3:16 ` Po Lu
2021-09-05 4:29 ` Hongyi Zhao
2021-09-05 7:34 ` Po Lu
2021-09-05 8:02 ` Hongyi Zhao
2021-09-06 1:06 ` Po Lu
2021-09-04 13:47 ` Kévin Le Gouguec
2021-09-04 13:58 ` Hongyi Zhao
2021-09-04 23:25 ` Philip Kaludercic
2021-09-07 15:09 ` Max Nikulin
2021-09-08 2:02 ` Po Lu
2021-09-08 17:34 ` Max Nikulin
2021-09-08 22:49 ` Tim Cross
2021-09-09 6:12 ` Eli Zaretskii [this message]
2021-09-10 3:39 ` Richard Stallman
2021-09-16 17:24 ` Max Nikulin
2021-09-16 21:03 ` chad
2021-09-19 17:01 ` Max Nikulin
2021-09-08 17:38 ` Dmitry Gutov
2021-09-04 14:04 ` Ben Mezger
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=83h7eul1k9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=theophilusx@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).