From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: pull requests Date: Fri, 27 Mar 2020 18:21:35 +0300 Message-ID: <83eetd962o.fsf@gnu.org> References: <87mu87ji39.fsf@dick> <87v9mvp2ms.fsf@blind.guru> <87d093f6lj.fsf@dick> <87369yc79r.fsf@dick> <83mu828c7d.fsf@gnu.org> <7b0e82fd-8928-26d2-4bed-331593685f36@gmail.com> <83h7ya7wne.fsf@gnu.org> <8b7d5a28-8193-cd12-bb47-b70c7eee6db5@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="63454"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: =?utf-8?Q?Cl=C3=A9ment?= Pit-Claudel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Mar 27 16:23:28 2020 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 1jHqpU-000GPE-GH for ged-emacs-devel@m.gmane-mx.org; Fri, 27 Mar 2020 16:23:28 +0100 Original-Received: from localhost ([::1]:43006 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jHqpT-00045c-C1 for ged-emacs-devel@m.gmane-mx.org; Fri, 27 Mar 2020 11:23:27 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42279) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jHqnn-0001CU-S5 for emacs-devel@gnu.org; Fri, 27 Mar 2020 11:21:45 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:41949) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1jHqnm-0004za-RM; Fri, 27 Mar 2020 11:21:42 -0400 Original-Received: from [176.228.60.248] (port=2522 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jHqnl-0006UM-3c; Fri, 27 Mar 2020 11:21:42 -0400 In-Reply-To: <8b7d5a28-8193-cd12-bb47-b70c7eee6db5@gmail.com> (message from =?utf-8?Q?Cl=C3=A9ment?= Pit-Claudel on Fri, 27 Mar 2020 10:37:38 -0400) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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" Xref: news.gmane.io gmane.emacs.devel:245840 Archived-At: > Cc: emacs-devel@gnu.org > From: Clément Pit-Claudel > Date: Fri, 27 Mar 2020 10:37:38 -0400 > > >> Assuming you use the web UI, you can typically attach comments to code regions. > > > > And how does one point to such past discussions, or more generally > > make sure they end up in some centralized place we could later > > revisit? > > These comments survive even after the pull request is merged, so the tracker that hosted the discussion and the code comments acts as that centralized place. So we are supposed to keep pointers to those sites, and use them? How do we know which site holds what relevant discussions? who will remember that several years after the discussion took place? And what if the tracker that hosted the discussion goes dark (e.g., because the person who submitted the patch is no longer keeping the branch, or simply because the hosting service is discontinued? I really don't see how a project that is 30-something years old, and intends to live for several more decades, can possibly rely on such infrastructure for discussions that might prove important years from now. We must have all these archives in a single place, which we can control and which we can ensure continues to be available for years to come.