From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: FETCH_HEAD files and mirrored repos
Date: Sun, 12 Jul 2020 16:25:02 -0400 [thread overview]
Message-ID: <20200712202502.x4p2c7rf6ctflt5g@chatter.i7.local> (raw)
In-Reply-To: <xmqqblkkr63u.fsf@gitster.c.googlers.com>
On Sun, Jul 12, 2020 at 10:33:09AM -0700, Junio C Hamano wrote:
> >> So, unless your script depends on the presence and/or the contents
> >> of FETCH_HEAD, you can safely remove it.
> >
> > Excellent, that just saved me 20G per each mirror. :)
>
> Meaning that minimum 4k per file adds up that much due to 5 millions
> of repositories, or something?
Gosh, no. Only 28,000 repositories, with many FETCH_HEAD files being a
few MB in size.
I also discovered that symlinking FETCH_HEAD to /dev/null works as well
and thus saves a few IO cycles.
-K
next prev parent reply other threads:[~2020-07-12 20:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-11 20:48 FETCH_HEAD files and mirrored repos Konstantin Ryabitsev
2020-07-11 21:07 ` Junio C Hamano
2020-07-11 21:19 ` Konstantin Ryabitsev
2020-07-12 17:33 ` Junio C Hamano
2020-07-12 20:25 ` Konstantin Ryabitsev [this message]
2020-07-12 20:52 ` Junio C Hamano
2020-07-12 21:54 ` Konstantin Ryabitsev
2020-07-13 17:09 ` Johannes Sixt
2020-07-13 17:13 ` Junio C Hamano
2020-07-13 18:06 ` [PATCH] fetch: optionally allow disabling FETCH_HEAD update Junio C Hamano
2020-07-13 19:08 ` Taylor Blau
2020-07-13 19:45 ` Junio C Hamano
2020-07-13 20:00 ` FETCH_HEAD files and mirrored repos Konstantin Ryabitsev
2020-07-13 20:04 ` Junio C Hamano
2020-07-13 20:22 ` Jeff King
2020-07-13 20:34 ` Konstantin Ryabitsev
2020-07-13 20:50 ` Jeff King
2020-07-13 20:43 ` Johannes Sixt
2020-07-14 4:11 ` Jonathan Nieder
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200712202502.x4p2c7rf6ctflt5g@chatter.i7.local \
--to=konstantin@linuxfoundation.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).