From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Dmitry Alexandrov Newsgroups: gmane.lisp.guile.devel Subject: Re: pull requests for guile Date: Mon, 08 May 2023 14:32:02 +0300 Message-ID: References: <781a3ed7-6fcd-b502-a03b-6ae63279be75@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="7432"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) Cc: guile-devel@gnu.org To: Matt Wette Original-X-From: guile-devel-bounces+guile-devel=m.gmane-mx.org@gnu.org Mon May 08 13:32:55 2023 Return-path: Envelope-to: guile-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 1pvz6t-0001lh-3a for guile-devel@m.gmane-mx.org; Mon, 08 May 2023 13:32:55 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pvz6Q-0005yO-6S; Mon, 08 May 2023 07:32:29 -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 1pvz6C-0005xv-2p for guile-devel@gnu.org; Mon, 08 May 2023 07:32:17 -0400 Original-Received: from msg-2.mailo.com ([213.182.54.12]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pvz68-0005hv-SG for guile-devel@gnu.org; Mon, 08 May 2023 07:32:11 -0400 Original-Received: by b221-4.in.mailobj.net [192.168.90.24] with ESMTP via ip-20.mailobj.net [213.182.54.20] Mon, 8 May 2023 13:32:04 +0200 (CEST) X-EA-Auth: Ue1FjL/4zdo1pQzc5cTkTc6hFf8ex9GKW5R3L0ehcs7uHhKr81mK89m1gMiJSOeGfKrDhZMGs3ZwR5cprqe/rJo0DaieG+Vq In-Reply-To: <781a3ed7-6fcd-b502-a03b-6ae63279be75@gmail.com> (Matt Wette's message of "Sat, 6 May 2023 09:21:33 -0700") Received-SPF: pass client-ip=213.182.54.12; envelope-from=dag@gnui.org; helo=msg-2.mailo.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-devel-bounces+guile-devel=m.gmane-mx.org@gnu.org Original-Sender: guile-devel-bounces+guile-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.lisp.guile.devel:21825 Archived-At: --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Matt Wette wrote: > Does the savannah git repo support `git-request-pull'? To the best of my knowledge, no any server-side support is required for tha= t. Git is intentionally designed to avoid any reliance on servers as much as p= ossible. > And if so, would that make getting patches in more efficient? I would like to double that question with no any particular connection to G= uile. I fully understand why many developers generally refuse to review freeform = pull requests and ask to send patches via their favourite integrated platfo= rm (such as gitlab or github) =E2=80=94 anyone can evaluate extra features = they provide. Yet, I fail to get why so many teams insist that patches must be submitted = as per git-format-patch. Evidently, this is because they habitually rely on some tooling, that expec= ts patchsets in that format. But what is that tooling? The only thing the I am aware of is git-am, which provides... nothing (?) o= ver a simple pull request. There must be some bits of hidden knowledge, passed from generation to gene= ration of maintainers of venerable bazaar-style projects. ;-) So, I would be glad if Guile / Guix / etc patch-reviewers shared some detai= ls about their workflow. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iIMEARYIACsWIQRSX35grYEsI2F1K7TIsPhUjufz5wUCZFjdsg0cZGFnQGdudWku b3JnAAoJEMiw+FSO5/Pnbr0A/jJ0er88WIuP55P8dTevpv7vwj/unmt+aXbiPX4a MzS0AQD7NotvovVRY7eOSQbO79J43Cf3IxlnyzDV4NPwg+x/AQ== =V5Qy -----END PGP SIGNATURE----- --=-=-=--