git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Miłosz Kosobucki" <mikom3@gmail.com>
To: git@vger.kernel.org
Subject: Cleanup tool for old blobs in partial clone
Date: Fri, 11 Dec 2020 13:03:21 +0100	[thread overview]
Message-ID: <6446f471-87ed-9fc4-fd54-61c5cf95a218@gmail.com> (raw)

Hello,

I recently looked into the partial clone functionality and how it could 
be used to replace Git LFS.

Let's say that I use partial clone where one directory is filtered out 
through --filter=sparse:oid=XXX. Let's also say it's a directory with 
big assets for a computer game.

Now, as the project progresses and new versions of assets are checked 
in, I'll accumulate many version of these assets as I get new versions. 
I won't need them though, because most of the time I'm interested only 
in the latest version.

So my question is: is there some tool (probably similar to git lfs 
prune) that will let me get rid of the blobs that I don't need anymore?

I couldn't find information about it anywhere in the docs. I vaguely 
remember a mention of something like that possibly being done in the 
future in partial clone (or maybe promisor remote?) patch mails but I 
couldn't find it again.

Best regards,
-- 
Miłosz Kosobucki

             reply	other threads:[~2020-12-11 12:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-11 12:03 Miłosz Kosobucki [this message]
2020-12-13 10:10 ` Cleanup tool for old blobs in partial clone Christian Couder
2020-12-15 21:41   ` Miłosz Kosobucki

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=6446f471-87ed-9fc4-fd54-61c5cf95a218@gmail.com \
    --to=mikom3@gmail.com \
    --cc=git@vger.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.
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).