From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS31976 209.132.180.0/23 X-Spam-Status: No, score=-3.9 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, RCVD_IN_DNSWL_HI,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE, SPF_NONE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by dcvr.yhbt.net (Postfix) with ESMTP id 359231F619 for ; Thu, 12 Mar 2020 04:02:54 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727033AbgCLECx (ORCPT ); Thu, 12 Mar 2020 00:02:53 -0400 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:57479 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725980AbgCLECx (ORCPT ); Thu, 12 Mar 2020 00:02:53 -0400 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 168EB21FA7 for ; Thu, 12 Mar 2020 00:02:52 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Thu, 12 Mar 2020 00:02:52 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jramsay.com.au; h=from:to:subject:date:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mesmtp; bh=WxTHbiev3t0qzyEj3Q81AEMRo0deiRrCnFCCB+q5FeM=; b=MxPm7kAs1B1c jWA4EVW5U5jM1RTEemhrqKdLoE/qU1AWvaHg1vKAByZ8ba1oTwAN3bhxwZPHLzrk xsceQJnUHXgJ4jmZE0OAnf/O3KSxAwR6ewFtl1Hmx1F3F3OBvB4H/j/n+/sI+Trl bBxU0+KwMe3E6PXvPo7xuBOdUDpU2Ao= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=WxTHbiev3t0qzyEj3Q81AEMRo0deiRrCnFCCB+q5F eM=; b=SiuUk3eGXQOTRmfOaD0nHDCQI0I3yoZEyItbY+SOirpAjR+EuBMAGJDsS xH6RGYez1jlmosefw2IlsEvs7oT/lt7v4XU8xCyDvyC9DpG0DTIVVHLCrEZQ5tcl njHHb1pmxVDDaeDghQS4TVgEzbXpvpcxpxi0pWuhbsggUsIv/a1qztAIy8lpcT1Y cVDLzrz4Cd1LSv05KZqSISoM6fckX7wXqdTmU2gCcww2hI7ZUt4uLW1M30LSgrQc z8hJ+Y0xkV5w/TYVNAR8Bor+UpTbnO4DSiYbzAe0WsU2tTxaKaZj9gsL0YjgYA8x 2dTSAJhVeiQAN9rldlTbocEoC2xsg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedruddvgedgjeekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhvffufffokfgjfhggtgfgsehtke hmtdertdejnecuhfhrohhmpedflfgrmhgvshcutfgrmhhsrgihfdcuoehjrghmvghssehj rhgrmhhsrgihrdgtohhmrdgruheqnecukfhppeduvddurddvtddtrdeirdduuddtnecuve hluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepjhgrmhgvshes jhhrrghmshgrhidrtghomhdrrghu X-ME-Proxy: Received: from [192.168.1.38] (121-200-6-110.79c806.syd.nbn.aussiebb.net [121.200.6.110]) by mail.messagingengine.com (Postfix) with ESMTPA id 6A568328005E for ; Thu, 12 Mar 2020 00:02:51 -0400 (EDT) From: "James Ramsay" To: git@vger.kernel.org Subject: [TOPIC 7/17] Background operations/maintenance Date: Thu, 12 Mar 2020 15:02:48 +1100 X-Mailer: MailMate (1.13.1r5671) Message-ID: <35FDF767-CE0C-4C51-88A8-12965CD2D4FF@jramsay.com.au> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org 1. Stolee: Are we interested in having a background process doing things? 2. Emily: There are a lot of different ways to do this. Even only looking at Linux there are different ways. 3. Stolee: Without looking at how? What background operations would we like to have? 4. Emily: Is it a good candidate for `git undo`? To keep track of what the user was doing and to make it possible to roll back? 5. Brian: It can run into scalability issues. Also there might be repos on my disk that never change and don’t need background processing. At GitHub we do maintenance based on the number of pushes. 6. Stolee: Kind of maintenance will differ from client and server, interests are different. For Scalar we have this one process looking at all repos and will do operations on them. 7. Peff: On server-side you’ll have millions of repos and even one process looking at all processes have impact on the system. Most hosting providers already have services taking care of this, so I think this feature is only interesting for client-side. 8. Brian: We should be careful. For example I’m constantly creating test repos in /tmp. 9. Stolee: Thanks for the input, we’ll do research and come back to this.