From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-3.7 required=3.0 tests=AWL,BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, RCVD_IN_DNSWL_HI,SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.6 Received: from out1.vger.email (out1.vger.email [IPv6:2620:137:e000::1:20]) by dcvr.yhbt.net (Postfix) with ESMTP id 88D2E1F5A0 for ; Fri, 3 Feb 2023 04:02:50 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=mit.edu header.i=@mit.edu header.a=rsa-sha256 header.s=outgoing header.b=ixKpE/Ps; dkim-atps=neutral Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231836AbjBCECn (ORCPT ); Thu, 2 Feb 2023 23:02:43 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41644 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231725AbjBCECi (ORCPT ); Thu, 2 Feb 2023 23:02:38 -0500 Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 94B8A14EBD for ; Thu, 2 Feb 2023 20:02:37 -0800 (PST) Received: from cwcc.thunk.org (pool-173-48-120-46.bstnma.fios.verizon.net [173.48.120.46]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 31342WdW025336 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 2 Feb 2023 23:02:33 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mit.edu; s=outgoing; t=1675396954; bh=qqKOvwfHWvGTB2R6+jlE/otM2kd7vgL2B4XGhhibRdM=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=ixKpE/PsIkLL3MvAAvzN82glpx+PFpLaoMxN/SE252XO1eQXzp/l/ay+WXTTID4Zm PEVTvy07uMTkvSl5q3UscRtrn0ltcYHvr/bGX7mfiJNnZpkSOvzB8kJFpr/l+8upqn xHLOcgs3qvVbKGwEuOZFUTX2jmhQ8nQJ9t2XFlXElmZ9Vatc2DI5ejnhsncrz0AuJ2 0SraoMFb2oVtVdL2CjN6thYqM/6Eb8ODwuHWvSOzJA/djCDjI0o6y+1fiRD9PhVOlx Ispo5VSAKk2yccDuPnhx1zNjAShsnh1BwTiUKL1sILUBg/SUyfkeQZKZcRrX04jVl/ BAMoIyXmHDNlw== Received: by cwcc.thunk.org (Postfix, from userid 15806) id 93C5D15C340F; Thu, 2 Feb 2023 23:02:32 -0500 (EST) Date: Thu, 2 Feb 2023 23:02:32 -0500 From: "Theodore Ts'o" To: Joey Hess Cc: Git List Subject: Re: Stability of git-archive, breaking (?) the Github universe, and a possible solution Message-ID: References: <20230131150555.ewiwsbczwep6ltbi@meerkat.local> <230201.86pmatr9mj.gmgdl@evledraar.gmail.com> <20230201122152.GJ19419@kitsune.suse.cz> <230201.86cz6tqyvy.gmgdl@evledraar.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org On Thu, Feb 02, 2023 at 05:19:30PM -0400, Joey Hess wrote: > In my opinion as the original developer of pristine-tar, it's too > complicated to be usefully used by git. The problem it solves is of a > larger scope than the problem git has here. (I hope.) Well, the problem which I believe folks on this thread are trying to deal with is a way to reconstruct a bit-for-bit compressed tarball of a particular release in a way that minimizes the cost of storage in the git tree. One way of doing that would be to guarantee that git archive would return something which is always bit-for-bit identical. Another way is to use something like pristine tar. I'll grant that pristine tar does solve a bit more of the problem than what has been stated, since it allows the creator of the tarball to remove some files, or add some auto-generated files (e.g., after running autoreconf), and so in that way, pristine tar does solve a somewhat larger problem than what was expressed in this thread. That being said, however, pristine-tar is **extremely** useful, and I'm very happy, and very thankful, that you wrote it. It has been super, super useful. Cheers, - Ted