From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 61FA3C636CD for ; Tue, 31 Jan 2023 19:11:26 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231726AbjAaTLZ (ORCPT ); Tue, 31 Jan 2023 14:11:25 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59146 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229969AbjAaTLU (ORCPT ); Tue, 31 Jan 2023 14:11:20 -0500 Received: from mail-wr1-x42b.google.com (mail-wr1-x42b.google.com [IPv6:2a00:1450:4864:20::42b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A823859B6D for ; Tue, 31 Jan 2023 11:10:59 -0800 (PST) Received: by mail-wr1-x42b.google.com with SMTP id h12so15177584wrv.10 for ; Tue, 31 Jan 2023 11:10:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=LWQaPUHdvnU65mQKid3pXmNQLFqWKjlrZ1lOgMgLH+s=; b=KRhy5frvJMVHgXhqQrlHounxae4upCd0hrESJBpOq5WU1qL7Uzbhat0uhXVNpYQhTz b9qVSdLZ7CueM1UBOwhymX1jMWKQRypoS5c49CeHKgAAs0dE/qDA2mMfiuYW7kV7eqws ZKoyZjP0TA6ytqwMBYJJowiBgQrWiNRHmF+5aVU9vCeaXd1WYmsLVZAoKeT83z4U0lHX cWCyQO8vleafzBGlRQE+ooU7gCuD8T/cDGFxZizak+VXnZ6mQLG4TZUMrXCnh3rJFxaW kx7wJk4eKPBG5/kU4Qj+wA0ZtXg4vcfuLvbKiOeskhSuOjFGtXbeAxc6Rj7ywThFIYOE 7AQQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=LWQaPUHdvnU65mQKid3pXmNQLFqWKjlrZ1lOgMgLH+s=; b=yZ/qjkcw4mnX2dGL2NvBJrGcVMycpJwBflCF4w6ddrafKh030tfR9chTXYgRbvHgm7 I5osa3u7sqwJLvn0VdlLT+nORMTdHp8VR5ruyIv6Ivxpo9hqB9lNDbqriR9QBBVFGVVU ATESSq5JwSkGa+xua7SFF3BZbNMaW8Brnqf6EWS0m//YZSx9Zhf5Hs5MNy1iXvpdFsZe 84GVyarctvDWAwLov+S7P4IpmKZZrVBRxOlBzIQawVi87Hr6A31FVnasytgD8l5EDgZn yPMvgZvo6d8OmAEHJ5hvdCQLgksydf1IDIzrPQ1pY6rlvjRLtgWvu+2GyXi+EoQkRH0v lnBA== X-Gm-Message-State: AO0yUKVp3vIHbe1Ll2tUm4HAqWq6yRfQuvvCCJ9hwp/a7bq0iSZAY1wf ddlsFbfj5AHbNM6ReVbi96aIbg== X-Google-Smtp-Source: AK7set8y+W5CT0CBXGADEv6jw70U8BiynRGR11vPErBj7/6RMyebIrDMuBfwqBhI7I+SzvnxeImg9A== X-Received: by 2002:a5d:6b89:0:b0:2bf:b571:1f18 with SMTP id n9-20020a5d6b89000000b002bfb5711f18mr74635wrx.61.1675192255852; Tue, 31 Jan 2023 11:10:55 -0800 (PST) Received: from [192.168.1.109] ([178.197.216.144]) by smtp.gmail.com with ESMTPSA id j9-20020a5d6189000000b002c285b4d2b5sm2516469wru.101.2023.01.31.11.10.51 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 31 Jan 2023 11:10:55 -0800 (PST) Message-ID: Date: Tue, 31 Jan 2023 20:10:50 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 Subject: Re: [PATCH] .gitignore: Keep track of archived files as they are added to a new git repo Content-Language: en-US To: Like Xu , Will Deacon , Paolo Bonzini , Masahiro Yamada Cc: Catalin Marinas , Shuah Khan , Miguel Ojeda , Wedson Almeida Filho , Alex Gaynor , Kees Cook , Andrew Davis , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kselftest@vger.kernel.org, kvm@vger.kernel.org References: <20230130090426.13864-1-likexu@tencent.com> From: Krzysztof Kozlowski In-Reply-To: <20230130090426.13864-1-likexu@tencent.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 30/01/2023 10:04, Like Xu wrote: > From: Like Xu > > With thousands of commits going into mainline each development cycle, > the metadata .git folder size is gradually expanding (1GB+), and for some > developers (most likely testers) who don't care about the lengthy git-log, > they just use git-archive to distribute a certain version of code (~210MB) > and rebuild git repository from anywhere for further code changes, e.g. > > $ git init && git add . -A > > Then unfortunately, the file tracking metadata from the original git-repo > using "git add -f" will also be lost, to the point where part of source > files wrapped by git-archive may be accidentally cleaned up: > > $ git clean -nxdf > Would remove Documentation/devicetree/bindings/.yamllint https://lore.kernel.org/all/20230127150225.18148-1-andriy.shevchenko@linux.intel.com/ Best regards, Krzysztof