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-Status: No, score=-3.8 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by dcvr.yhbt.net (Postfix) with ESMTP id 70B471F55B for ; Thu, 28 May 2020 00:48:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725905AbgE1AsD (ORCPT ); Wed, 27 May 2020 20:48:03 -0400 Received: from pb-smtp20.pobox.com ([173.228.157.52]:63459 "EHLO pb-smtp20.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725891AbgE1AsC (ORCPT ); Wed, 27 May 2020 20:48:02 -0400 Received: from pb-smtp20.pobox.com (unknown [127.0.0.1]) by pb-smtp20.pobox.com (Postfix) with ESMTP id B6905C6726; Wed, 27 May 2020 20:48:00 -0400 (EDT) (envelope-from junio@pobox.com) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; s=sasl; bh=IPZ2GOs9HRSYVOd7ryFAOZp9fWQ=; b=vqPt7Q nlK/z5z+bx2HhOlpobIk7xQkQ15Iab6w5YxcXKdEC+OfxMTl4ocgEO59QtxBTvv4 mM2CuciKuBH8UlMtyORt8Ws6VRy43pX0OdUeg0RWQj+To3uTX5W3468NPi6lVw9n IFZgFR0JFnZkOkn05Bc3SGkoiylC2D688qtCM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; q=dns; s=sasl; b=DysuI0YMGnWoFSAI+RMvDI7ATWtBmwDd sLwx+n7fHfHPWkTaITZUbmve3tuh4H9DGxvxheCmCXiRojcJTgl7Of3XxtRu1Jlu SmhzJi8g0NeWsSSy5NxKZSEo9/HjtNNGwbw24/lPa2t+LYsZ9N/uIwj93Xr4Ldvk 9ljb5IefMMg= Received: from pb-smtp20.sea.icgroup.com (unknown [127.0.0.1]) by pb-smtp20.pobox.com (Postfix) with ESMTP id AEE02C6725; Wed, 27 May 2020 20:48:00 -0400 (EDT) (envelope-from junio@pobox.com) Received: from pobox.com (unknown [35.196.173.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp20.pobox.com (Postfix) with ESMTPSA id A5D03C6724; Wed, 27 May 2020 20:47:56 -0400 (EDT) (envelope-from junio@pobox.com) From: Junio C Hamano To: Josh Steadmon Cc: "brian m. carlson" , Johannes Schindelin , Derrick Stolee , Derrick Stolee via GitGitGadget , git@vger.kernel.org, peff@peff.net, jrnieder@google.com, Derrick Stolee Subject: Re: [PATCH 00/15] [RFC] Maintenance jobs and job runner References: <20200407014829.GL6369@camp.crustytoothpaste.net> <20200408000149.GN6369@camp.crustytoothpaste.net> <20200527223907.GB65111@google.com> Date: Wed, 27 May 2020 17:47:55 -0700 In-Reply-To: <20200527223907.GB65111@google.com> (Josh Steadmon's message of "Wed, 27 May 2020 15:39:07 -0700") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Pobox-Relay-ID: DF0FB0B6-A07C-11EA-93C4-B0405B776F7B-77302942!pb-smtp20.pobox.com Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Josh Steadmon writes: > Regardless of what happens with the job-runner, I would like to see a > top-level command that performs a single iteration of all the > recommended maintenance steps, with zero configuration required, on a > single repo. This gives an entry point for users who want to manage > their own maintenance schedule without running a background process. > ... >> Unix users will be unhappy with us if we use our own scheduling system >> when cron is available. They will expect us to reimplement those >> features and they will complain if we do not. While I cannot name >> names, there are a nontrivial number of large, enterprise monorepos that >> run only on macOS and Linux. > > Speaking purely as a user, I agree with this point. This is why I want a > single-iteration top-level maintenance command. Yes, well said. It exactly is what "git gc" was meant to be. To put it differently, if you asked any non-novice end-user if there is one single command that s/he would use to keep a repository healthy, it is very likely that the answer would be "git gc". And having such a single point of entry would be a good thing. Thanks.