From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: contributing to Emacs Date: Sun, 18 Jun 2023 13:36:05 +0300 Message-ID: <83mt0xnjl6.fsf@gnu.org> References: <83v8fnslfz.fsf@gnu.org> <87v8fnh1h2.fsf@web.de> <83mt0zs9rc.fsf@gnu.org> <0a968a4e1b267c0f15dd237e6ea12a709fc06d5e.camel@yandex.ru> <838rcisj7o.fsf@gnu.org> <6537fa5fa5c1fe8437ed99ee0988e35895f5a54b.camel@yandex.ru> <8423a35750d8d8e0437c7708f6b4d0bbdfdb7fe0.camel@yandex.ru> <87o7ldf7ky.fsf@web.de> <8cc19084ab18d0adb0f2cee4af14aa1b1d914a83.camel@yandex.ru> <83sfapnl57.fsf@gnu.org> <83pm5tnk78.fsf@gnu.org> <73cbe80096cd97728fcdaccf9f9badeea606570b.camel@yandex.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="12576"; mail-complaints-to="usenet@ciao.gmane.io" Cc: arne_bab@web.de, ams@gnu.org, luangruo@yahoo.com, emacs-devel@gnu.org To: Konstantin Kharlamov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Jun 18 12:36:51 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qApm6-00032E-RM for ged-emacs-devel@m.gmane-mx.org; Sun, 18 Jun 2023 12:36:50 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qAplQ-00054m-1N; Sun, 18 Jun 2023 06:36:08 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qAplN-00054R-IV for emacs-devel@gnu.org; Sun, 18 Jun 2023 06:36:05 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qAplM-0005Dh-Dv; Sun, 18 Jun 2023 06:36:04 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=PFh+PpRb5ZqosLPYLbslZjZ/ZDWz2EjHSK9ucQnVIoo=; b=VRXd15eR3kN+enC3zxxB vK6xxYTOijKk2Ab5BCIyaPcL4o1WyrVbAeUoYKhwXCzyZNQCOEJDMa3o2xqUWezKjTwra1p9Lfw4s Vh/81SUSseF8thXKVFCzDvUmIEkQFd1YzwbJTbi2o093seNlRqqn5L9kW34s/ZpgoBOb8ZEe/Dc06 tdZqvMQ5GCt4CMlFzOYLiWWzZUyyUR70U5+ES0az926NmXuEImduRwHMWzt4DVj1EGCEOWtCFm8zz keRRrIQLYyPrAVdANJf1sjk8p+m8OwhIHAZjtKjhKkj46d82t9NoeEcl+a9+jNwOziGiMERVWNSeR UVwQQSQ2K3rzNw==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qAplL-0004Mu-9r; Sun, 18 Jun 2023 06:36:03 -0400 In-Reply-To: <73cbe80096cd97728fcdaccf9f9badeea606570b.camel@yandex.ru> (message from Konstantin Kharlamov on Sun, 18 Jun 2023 13:27:47 +0300) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:306957 Archived-At: > From: Konstantin Kharlamov > Cc: arne_bab@web.de, ams@gnu.org, luangruo@yahoo.com, emacs-devel@gnu.org > Date: Sun, 18 Jun 2023 13:27:47 +0300 > > > Like I said: we prefer a single patch for each changeset.  The > > problems presented by patch series are one reason.  And yet, we will > > never reject a patch series, even though it makes the process > > inconvenient and confusing. > > > > I don't see what else do we need to argued about here. > > Well, you see, the "sending patches" section has no mention that a series is > unwelcome. They aren't "unwelcome", please don't misquote what I write. > If series is indeed unwelcome, it would be better to reflect in "sending > patches" section and provide copy-paste instructions for the people to quickly > squash their commits before sending to ML (and I think something needs to be > figured out about commit messages too in this case). Because when you are > developing, it is easier to separate changes to distinct commits to make sure > that if something break you know what exactly change was the reason to it. Even > if these commits will have to be squashed later. It sounds like you have just asked us to make that section larger, is that right?