From: Philip Kaludercic <philipk@posteo.net>
To: Hongyi Zhao <hongyi.zhao@gmail.com>
Cc: "Po Lu" <luangruo@yahoo.com>,
Emacs-devel@gnu.org,
"Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Subject: Re: Why not set Emacs development workflow based on the popular git forges (GitHub, Bitbucket, Gitlab, ect)?
Date: Sat, 04 Sep 2021 23:25:59 +0000 [thread overview]
Message-ID: <87lf4bapo8.fsf@posteo.net> (raw)
In-Reply-To: <CAGP6PO+gX7DrJLDthMtwXePD_RkOP8=6Hhd+-i4a=7o-E5-kSw@mail.gmail.com> (Hongyi Zhao's message of "Sat, 4 Sep 2021 21:58:04 +0800")
Hongyi Zhao <hongyi.zhao@gmail.com> writes:
> Sending patches isn't quite as simple as sending a pull request, but
> fortunately it is a well documented process.
It depends, I have certainly had times where sending a patch was easier
than preparing a pull request. One thing that was mentioned in the other
thread is that people are not used to patches on mailing
lists. Sourcehut and specifically git-send-email.io came up with the
clever idea of providing a testing list that nobody reads, just to see
how their messages will end up looking like. As long as you don't have
to worry that any small small mistake will have an army of greybeards
shouting at you for messing up, I think people are more accepting of a
different workflow (or that is at least my experience).
--
Philip Kaludercic
next prev parent reply other threads:[~2021-09-04 23:25 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 [this message]
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
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=87lf4bapo8.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=Emacs-devel@gnu.org \
--cc=hongyi.zhao@gmail.com \
--cc=kevin.legouguec@gmail.com \
--cc=luangruo@yahoo.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).