From: <tomas@tuxteam.de>
To: Hongyi Zhao <hongyi.zhao@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: Sat, 4 Sep 2021 09:13:20 +0200 [thread overview]
Message-ID: <20210904071320.GC3280@tuxteam.de> (raw)
In-Reply-To: <CAGP6POLOqSZ0HzkBa_QgPyvs=1Q4fqSve-7L6h3ZcxY-LN1bng@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 710 bytes --]
On Sat, Sep 04, 2021 at 02:55:35PM +0800, Hongyi Zhao wrote:
> Nowadays, the large software projects often conduct the development on
> the workflow supplied by git forges (GitHub, Bitbucket, GitLab,
> etc.). But it seems that Emacs is still developed directly on git, as
> described here [1], which makes maintaining GNU Emacs development a
> lot of extra work.
>
> So, why not set Emacs development workflow based on the popular git forges?
There is an enormous discussion about this in this very mailing list
(starting around endo of August and still ongoing, with well over
300 posts.
Are you aware of it? Perhaps there might be some iteresting aspects
in there for you.
Cheers
- t
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2021-09-04 7:13 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 [this message]
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
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=20210904071320.GC3280@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=Emacs-devel@gnu.org \
--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).