From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.help Subject: Re: Why is Elisp slow? Date: Sun, 05 May 2019 15:19:03 +0200 Message-ID: <87ef5davjs.fsf@telefonica.net> References: <83muk4obfd.fsf@gnu.org> <20190502214006.4fdsinp7u5xuqvdv@Ergus> <20190503004416.xfuzzucflp6bxpuz@Ergus> <20190503103644.63lccjehmzulaojn@Ergus> <456EE4D4-F542-4F6A-B146-E6B9D72AE93B@icloud.com> <83tvebn1we.fsf@gnu.org> <20190503125832.44ovncaxp3vyjsla@Ergus> <20190504133218.g3ysx3ksuyvlthg3@Ergus> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="50311"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sun May 05 15:20:36 2019 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hNH4G-000Czu-EN for geh-help-gnu-emacs@m.gmane.org; Sun, 05 May 2019 15:20:36 +0200 Original-Received: from localhost ([127.0.0.1]:41034 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hNH4F-0004Ba-Dr for geh-help-gnu-emacs@m.gmane.org; Sun, 05 May 2019 09:20:35 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:47949) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hNH2w-0003BC-H0 for help-gnu-emacs@gnu.org; Sun, 05 May 2019 09:19:15 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hNH2v-0007XA-I1 for help-gnu-emacs@gnu.org; Sun, 05 May 2019 09:19:14 -0400 Original-Received: from [195.159.176.226] (port=59650 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hNH2v-0007Wf-Bu for help-gnu-emacs@gnu.org; Sun, 05 May 2019 09:19:13 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.89) (envelope-from ) id 1hNH2s-000BbQ-Nn for help-gnu-emacs@gnu.org; Sun, 05 May 2019 15:19:10 +0200 X-Injected-Via-Gmane: http://gmane.org/ Cancel-Lock: sha1:JsjYHMcJzJCxj1kyVan54aMXGlY= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 195.159.176.226 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:120206 Archived-At: "Paul W. Rankin" writes: >> For the developers it is also easier to join to those projects >> because they are hosted on Github/gitlab with a more familiar >> workflow and interface, no copyright procedure, no mailing list.... >> and everything in the same please and integrate with a fork based >> workflow. You can see where I'm going right? > > If a possible contributor has cloned a project repository to their own > machine and has made some changes, the fork-based workflow requires > that they: create an account at the origin project's GitHub or GitLab > (or the project's GitLab instance), This is an one-off task. > create a forked repository there, Same. > add the fork as a remote on their machine, Same. > push the changes, then open a pull request. Which, in my experience, takes half a minute with the Github UI and possibly less with Magit's Github plugin. > Once you use a git send-email workflow, this fork-based workflow will > seem convoluted and unnecessarily centralised. All a contributor need > do is clone the project repository, commit some changes then run: > > git send-email HEAD^ You skipped over quite a few issues here. Plus, a branch is easy to access, in case someone wishes to grab the changes, while fishing mails on a mailing list requires more setup and constant attention. > And send the email to the project's owner/mailing list. No account > creation necessary. Check out: > > https://git-send-email.io/ Yes, that explains the job on a detailed way, and you can see that it is not as simple as you pretend. Plus, that's the setup for sending changes, no mention about how to grab them from the ml.