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 13:34:48 +0300 Message-ID: <1553250888.28810.2@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> 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="34714"; mail-complaints-to="usenet@blaine.gmane.org" Cc: theophilusx@gmail.com, emacs-devel@gnu.org, dgutov@yandex.ru To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Mar 22 11:35:33 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 1h7HWN-0008rf-SH for ged-emacs-devel@m.gmane.org; Fri, 22 Mar 2019 11:35:32 +0100 Original-Received: from localhost ([127.0.0.1]:55231 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h7HWM-00045a-TX for ged-emacs-devel@m.gmane.org; Fri, 22 Mar 2019 06:35:30 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:37584) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h7HVr-0003hT-TX for emacs-devel@gnu.org; Fri, 22 Mar 2019 06:35:00 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h7HVn-0004MU-Kn for emacs-devel@gnu.org; Fri, 22 Mar 2019 06:34:56 -0400 Original-Received: from forward102j.mail.yandex.net ([2a02:6b8:0:801:2::102]:40814) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1h7HVl-0004De-7u; Fri, 22 Mar 2019 06:34:54 -0400 Original-Received: from mxback8g.mail.yandex.net (mxback8g.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:169]) by forward102j.mail.yandex.net (Yandex) with ESMTP id 584CAF21AA7; Fri, 22 Mar 2019 13:34:50 +0300 (MSK) Original-Received: from smtp4p.mail.yandex.net (smtp4p.mail.yandex.net [2a02:6b8:0:1402::15:6]) by mxback8g.mail.yandex.net (nwsmtp/Yandex) with ESMTP id FjGcRZ7cv8-YoJC5k88; Fri, 22 Mar 2019 13:34:50 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1553250890; bh=n1HbbCyzsQevgy+mdKBZK+p6Javwh73r+YDAXPK4QaU=; h=In-Reply-To:Cc:To:Subject:From:References:Date:Message-Id; b=kY3TLeT7+a+RUOKuebJXbdK0nKXTi7JjCagWAcLqlIX3inafn2j5YEcA449ooPVkG +TZUVzxegDtaaiuUzM2kYca6CrucJKEG8BUUJ4ID/Iw0CKezj5p39TZy/fWxPndsK4 t34sj2P77TGx3gsYCQA8xrU8IKzZt8cDbVEb6kDM= Authentication-Results: mxback8g.mail.yandex.net; dkim=pass header.i=@yandex.ru Original-Received: by smtp4p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id wdHAgLpjKc-YnSiaLYU; Fri, 22 Mar 2019 13:34:49 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) In-Reply-To: <83ftrfrz6v.fsf@gnu.org> 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] X-Received-From: 2a02:6b8:0:801:2::102 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:234540 Archived-At: On =BF=E2, Mar 22, 2019 at 13:16:56, Eli Zaretskii wrote: >> And while on it, a few weeks ago I sent 2 patches to bugtrackers,=20 >> and I >> got a notification for each of them. I'm horrified to imagine what I >> gonna see if I send a series of 20 patches. >=20 > There's no requirement in Emacs development to send patches in series, > you can send a single patch for the entire changeset. then you will > get only one notification. This is odd, why would I do that? If somebody would squash 20 commits=20 into just one, and sent me for review, "break commits by functional"=20 would be my very first comment. How a reviewer supposed to give any=20 useful comments besides high-level stuff like "remove the commented out=20 code there", if a sigle patch does 20 functionally different changes? Furthermore: if such patch was commited, how other developers in the=20 future, while studying the git-log, are supposed to make any sense of=20 this commit? And how one supposed to git-bisect a regression with such a commit? =