unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: chad <yandros@gmail.com>
To: Max Nikulin <manikulin@gmail.com>
Cc: EMACS development team <emacs-devel@gnu.org>
Subject: Re: Why not set Emacs development workflow based on the popular git forges (GitHub, Bitbucket, Gitlab, ect)?
Date: Thu, 16 Sep 2021 14:03:16 -0700	[thread overview]
Message-ID: <CAO2hHWb6Fy0+rtOq3Fg=grM7_ZSDaxUsEax3Ee8Q6oesmZmOig@mail.gmail.com> (raw)
In-Reply-To: <shvuk8$543$1@ciao.gmane.io>

[-- Attachment #1: Type: text/plain, Size: 761 bytes --]

This is a small thing, but:

On Thu, Sep 16, 2021 at 10:25 AM Max Nikulin <manikulin@gmail.com> wrote:

>  My opinion is the following:
> [...]
> - The reason why current web UIs are not sufficient for Linux kernel
>    is not applicable for Emacs. There are a lot of independent groups
>    involved into kernel development while Emacs does not have such
>    fragmentation so flexibility in respect to groups is unnecessary.
>

I suspect that people who think this have never tried to follow, for
example, gnus, CEDET, or org development as part(s) of GNU emacs. These are
more common in the Linux kernel, but the core motivations exist in both
projects, and it would be great to have improvements even if they aren't
adopted by both.

Hope that helps,
~Chad

[-- Attachment #2: Type: text/html, Size: 1156 bytes --]

  reply	other threads:[~2021-09-16 21:03 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
2021-09-10  3:39             ` Richard Stallman
2021-09-16 17:24               ` Max Nikulin
2021-09-16 21:03                 ` chad [this message]
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='CAO2hHWb6Fy0+rtOq3Fg=grM7_ZSDaxUsEax3Ee8Q6oesmZmOig@mail.gmail.com' \
    --to=yandros@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=manikulin@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).