From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Like Xu <like.xu.linux@gmail.com>, Will Deacon <will@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Masahiro Yamada <masahiroy@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Shuah Khan <shuah@kernel.org>, Miguel Ojeda <ojeda@kernel.org>,
Wedson Almeida Filho <wedsonaf@google.com>,
Alex Gaynor <alex.gaynor@gmail.com>,
Kees Cook <keescook@chromium.org>, Andrew Davis <afd@ti.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kselftest@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH] .gitignore: Keep track of archived files as they are added to a new git repo
Date: Tue, 31 Jan 2023 20:10:50 +0100 [thread overview]
Message-ID: <ce9eb95b-bff6-c042-efbc-b42062d7cbf2@linaro.org> (raw)
In-Reply-To: <20230130090426.13864-1-likexu@tencent.com>
On 30/01/2023 10:04, Like Xu wrote:
> From: Like Xu <likexu@tencent.com>
>
> 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
prev parent reply other threads:[~2023-01-31 19:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 9:04 Like Xu
2023-01-30 16:06 ` Masahiro Yamada
2023-01-31 9:47 ` Like Xu
2023-01-31 19:10 ` Krzysztof Kozlowski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ce9eb95b-bff6-c042-efbc-b42062d7cbf2@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=afd@ti.com \
--cc=alex.gaynor@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=keescook@chromium.org \
--cc=kvm@vger.kernel.org \
--cc=like.xu.linux@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=ojeda@kernel.org \
--cc=pbonzini@redhat.com \
--cc=shuah@kernel.org \
--cc=wedsonaf@google.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®