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: Larger GC thresholds for non-interactive Emacs Date: Sat, 25 Jun 2022 11:28:55 +0300 Message-ID: <83ilopb0zc.fsf@gnu.org> References: <87bkurrc5e.fsf@localhost> <87bkur72b7.fsf@gnus.org> <874k0j40e7.fsf@gnus.org> <871qvm16he.fsf@gnus.org> <83a6aanm5j.fsf@gnu.org> <87o7yozzj0.fsf@gnus.org> <83k098kg6c.fsf@gnu.org> <8335fvg8kz.fsf@gnu.org> <87pmizrgoi.fsf@localhost> <83zgi3espf.fsf@gnu.org> <87pmizajtv.fsf@localhost> <83y1xneqif.fsf@gnu.org> <87mte3ah08.fsf@localhost> <83r13felor.fsf@gnu.org> <878rplwcp0.fsf@localhost> 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="35894"; mail-complaints-to="usenet@ciao.gmane.io" Cc: yantar92@gmail.com, owinebar@gmail.com, larsi@gnus.org, monnier@iro.umontreal.ca, mattiase@acm.org, theophilusx@gmail.com, rms@gnu.org, acm@muc.de, emacs-devel@gnu.org To: Yuri Khan Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jun 25 10:31:29 2022 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 1o51CS-0009C1-Pv for ged-emacs-devel@m.gmane-mx.org; Sat, 25 Jun 2022 10:31:28 +0200 Original-Received: from localhost ([::1]:52962 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o51CR-0007Bl-JT for ged-emacs-devel@m.gmane-mx.org; Sat, 25 Jun 2022 04:31:27 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36148) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o51A7-0005rI-7w for emacs-devel@gnu.org; Sat, 25 Jun 2022 04:29:03 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:55676) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o51A5-00057w-QI; Sat, 25 Jun 2022 04:29:01 -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=2yw/hHKhwbw+zRzoMV6ZmedoZebxBlnLYn6qJcdfz/U=; b=SOEQHMIHlX3x2BvsSEpD 0YXlpSQ0tf7TS2jOSQ3kXE3PItWuaO6bbkkpSnJYOgEjIXXEH3pZ7ELSzzmi9+L3ZpNBKQpfF15Q1 KblkWu9aB//hO8U8i8/m6KIKD/Po3fzJ6TCDk04lQAK1bt6HAEjva4Q1vhXd+tLs4lmE2m8j0JHtD 3OdD9N2PUUGiafw1YIo9KkPClZqx/eQicnGqUqUA6LFtXtZ1CunJlG6sS6TA2+efCyWmAxHLPzo1S FwW51wd97uiMt4Z89AncUJfVTaZfwUN04+N+XPs9vXw4YMuMPgkxRTRS5wPQLhzsET8EMc/ALIABv tbN3bNTaMuf8XQ==; Original-Received: from [87.69.77.57] (port=2022 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 1o51A3-0003ix-2X; Sat, 25 Jun 2022 04:29:00 -0400 In-Reply-To: (message from Yuri Khan on Sat, 25 Jun 2022 14:51:14 +0700) 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" Xref: news.gmane.io gmane.emacs.devel:291586 Archived-At: > From: Yuri Khan > Date: Sat, 25 Jun 2022 14:51:14 +0700 > Cc: Eli Zaretskii , owinebar@gmail.com, > Lars Magne Ingebrigtsen , Stefan Monnier , > Mattias EngdegÄrd , theophilusx@gmail.com, > Richard Stallman , Alan Mackenzie , Emacs developers > > On Sat, 25 Jun 2022 at 12:10, Ihor Radchenko wrote: > > > > What do you do with this when we change the VCS (which happened twice > > > already)? > > > > Of course, things will break if we change VCS, but it should not stop us > > from linking to commits - not linking at all is still worse. > > Identifying VCS commits in a way that is stable across VCS migration > is at least theoretically a solved problem. > http://esr.ibiblio.org/?p=3872 We considered that in the past, and decided to use a different method, see CONTRIBUTE. And in any case, the results of following that recommendation are before our eyes...