From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Konstantin Kharlamov Newsgroups: gmane.emacs.devel Subject: Re: [RFE] Migration to gitlab Date: Fri, 22 Mar 2019 14:24:56 +0300 Message-ID: <1553253896.18473.0@yandex.ru> References: <1552789070.5272.1@yandex.ru> <1552791707.5272.2@yandex.ru> <1552793646.5272.3@yandex.ru> <1552821396.21432.0@yandex.ru> <83imwhwf4x.fsf@gnu.org> <837ecvux2q.fsf@gnu.org> <9c7cf558-a2d3-951e-d6e1-31b3ad5900cf@yandex.ru> <1553064994.13109.0@yandex.ru> <831s32t3fn.fsf@gnu.org> <87mulnxkik.fsf@mbork.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-5; format=flowed Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="50290"; mail-complaints-to="usenet@blaine.gmane.org" Cc: Tim Cross , Emacs developers , Philippe Vaucher , Dmitry Gutov , Eli Zaretskii , Tadeus Prastowo To: Marcin Borkowski Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Mar 22 12:38:21 2019 Return-path: Envelope-to: ged-emacs-devel@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 1h7IVB-000Cvd-An for ged-emacs-devel@m.gmane.org; Fri, 22 Mar 2019 12:38:21 +0100 Original-Received: from localhost ([127.0.0.1]:55805 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h7IVA-0005d0-C4 for ged-emacs-devel@m.gmane.org; Fri, 22 Mar 2019 07:38:20 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:51633) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h7IU6-0005LR-5I for emacs-devel@gnu.org; Fri, 22 Mar 2019 07:37:17 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h7IIO-00025N-8j for emacs-devel@gnu.org; Fri, 22 Mar 2019 07:25:09 -0400 Original-Received: from forward104p.mail.yandex.net ([77.88.28.107]:48613) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1h7IIH-0001hq-UK; Fri, 22 Mar 2019 07:25:02 -0400 Original-Received: from mxback12g.mail.yandex.net (mxback12g.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:91]) by forward104p.mail.yandex.net (Yandex) with ESMTP id 4F9F74B018D4; Fri, 22 Mar 2019 14:24:59 +0300 (MSK) Original-Received: from smtp4j.mail.yandex.net (smtp4j.mail.yandex.net [2a02:6b8:0:1619::15:6]) by mxback12g.mail.yandex.net (nwsmtp/Yandex) with ESMTP id V35J8r5tdQ-Ow5K8C11; Fri, 22 Mar 2019 14:24:59 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1553253899; bh=anqgFxW6T8gYOqAJqTF/JIQDj2pc2C9/21Tof1lCjyI=; h=In-Reply-To:Cc:To:Subject:From:References:Date:Message-Id; b=fpLSXqrfJiqkVSpMZ9LYKn/qpqYGZrVTVKUDFJEQLB13zfEbZL3WlPtKoRpoPY/1X p2R/MEPDX23rNcpOzqAtIgWNb+la8uIMo7xKkL2LyGYY6aDewGLLJeYv3A6+NkoJTw 0mNtdiriik3XbrvrwUXeac7ZsrBZG8qO/niQ7cjo= Authentication-Results: mxback12g.mail.yandex.net; dkim=pass header.i=@yandex.ru Original-Received: by smtp4j.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id zcxOROUYe4-Ov1iBBZI; Fri, 22 Mar 2019 14:24:58 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) In-Reply-To: <87mulnxkik.fsf@mbork.pl> X-Mailer: =?UTF-8?Q?geary=2F=C3=8E=C2=B2=2Dtesting=2Dbran?= =?UTF-8?Q?ch=7Eg4db93c55?= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 77.88.28.107 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:234545 Archived-At: On =BF=E2, Mar 22, 2019 at 13:37:23, Marcin Borkowski =20 wrote: >=20 > On 2019-03-21, at 18:54, Philippe Vaucher=20 > wrote: >=20 >> As I said earlier, it's possible that adding the gitlab workflow=20 >> would >> yield 0 additional contributors, the only way to know for sure=20 >> would be to >> try it. Personnally I believe that at least for "typo fixes" and=20 >> tiny >> changes you'd get more contributions, because proposing a change on=20 >> the >> gitlab model is trivial (browse to the correct file, click "edit",=20 >> edit the >> file in your browser, press "propose changes", done). >>=20 >> Anway, what I am sure of is that if the gitlab workflow was added=20 >> there >> would be contributors on this ML (including me) that would use it=20 >> instead >> of the mailing list workflow. >=20 > Hi, >=20 > I loosely follow this discussion, but I'm curious: isn't a git branch > workflow equally well supported? I did contribute a bit to Emacs, and > what i did was push a feature branch and ask for it to be reviewed and > merged. Not quite what Gitlab does, but closer than sending patches=20 > by > email. This might work. I'd be afraid of sending patches on my own that way=20 because I don't know an attitude here to "making developers to access=20 stuff on unknown sites". But if that's supported, I'd definitely use it. Is this indeed supported? If yes, can we modify the=20 https://www.gnu.org/software/emacs/manual/html_node/emacs/Sending-Patches.h= tml=20 to include such workflow? =