From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: [OFFTOPIC] size of issue tracker (was: [RFE] Migration to gitlab) Date: Mon, 13 May 2019 12:41:25 -0400 Message-ID: References: <1552789070.5272.1@yandex.ru> <87imwhmmt8.fsf@gmail.com> <87y347g1l3.fsf@iotcl.com> <9ac21e82-8e47-f9b5-f88d-23c0c56946d1@yandex.ru> <87pnpc1lby.fsf@iotcl.com> <83zhoezdqc.fsf@gnu.org> <87imuivfcr.fsf@iotcl.com> <83k1eyfxls.fsf@gnu.org> <17D21056-10B2-4813-AE90-9B2706936CE9@icloud.com> <83imuifqjc.fsf@gnu.org> <87lfzehrug.fsf@gmail.com> <83k1exec2n.fsf@gnu.org> <8736lkikqf.fsf@gmail.com> <83y33cb5nc.fsf@gnu.org> <87a7fsf91l.fsf@gnu.org> <87pnongeju.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="98296"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: Eli Zaretskii , emacs-devel@gnu.org, toon@iotcl.com, Alex Gramiak , dgutov@yandex.ru To: Tassilo Horn Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon May 13 18:41:47 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 1hQE1K-000PTB-Cf for ged-emacs-devel@m.gmane.org; Mon, 13 May 2019 18:41:46 +0200 Original-Received: from localhost ([127.0.0.1]:60379 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hQE1J-0006CN-BH for ged-emacs-devel@m.gmane.org; Mon, 13 May 2019 12:41:45 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:37242) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hQE16-0006Ar-NE for emacs-devel@gnu.org; Mon, 13 May 2019 12:41:33 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hQE15-0007Yv-LM for emacs-devel@gnu.org; Mon, 13 May 2019 12:41:32 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:5198) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hQE13-0007Ws-Gw; Mon, 13 May 2019 12:41:29 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 28E2B4422B4; Mon, 13 May 2019 12:41:28 -0400 (EDT) Original-Received: from mail02.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id CE00C4422B2; Mon, 13 May 2019 12:41:26 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1557765686; bh=kO1hZB3kyklu8Hul+jBmTTY9xiLB8ivP3f85nLs0FhI=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=HoihBXmV4mibh2leovlNNWPWsOmxzNl7bQl9Hc0RFf6VtFNeiF6Z77u8LDvH/5Umm jDbRC6cGxWjvVZNy4tvnPQUDhdwpjBl0vx/AINUOvubGsPqAuRrcDaRFTviYC5YmOS Z/1VU2TbofUdJJX0/L/SfyFyQiLWBG+hiyUJr6SvORcnsTZXtEjuk1+hzRDebnEF3D o/QZvgimG6XUCtX6u15FcWu5DffkemPTGFY7AaMe7RmxwKIq4oqZgFa/KGsxYxzOaJ cEuI/Tze+0y+RH40XbzRzPLcItl/arZZLxOZTQUg6i1JourHyeMtIVm87YDBzALh/x 9nMzvTzHuz6lQ== Original-Received: from alfajor (69-196-155-191.dsl.teksavvy.com [69.196.155.191]) by mail02.iro.umontreal.ca (Postfix) with ESMTPSA id 81E1B120A58; Mon, 13 May 2019 12:41:26 -0400 (EDT) In-Reply-To: <87pnongeju.fsf@gnu.org> (Tassilo Horn's message of "Mon, 13 May 2019 06:32:21 +0200") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 132.204.25.50 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:236467 Archived-At: > Yesterday, after writing the above, I've checked out the gtk project and > enabled Magit/Forge on it. The initial fetch of the topics (~1900 > issues and ~800 merge requests) took about two hours, but contrary to > what has been reported in another message in this thread, it did not Not sure if this time is spent on turn-around time or actual transfer or what, but FWIW, my proof-of-concept BuGit issue-tracking-system kept the whole 20 thousand or so issues of debbugs.gnu.org in a Git repo that was less than 10MB, IIRC, so cloning the whole thing takes much less than 2 hours, even on a slow connection. One of the reasons why I really wish for a bug tracker that keeps the issues in Git (and no, sadly, BuGit is not up-to-the-task, it's just a 100KB proof-of-concept shell script). > Why does Forge insist downloading the entire DB to the local machine? > That sounds like something that wouldn't scale well. I don't know why it does so, but it sounds like a good idea to me, so you can later use them when you're offline. Stefan