git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Miłosz Kosobucki" <mikom3@gmail.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: Cleanup tool for old blobs in partial clone
Date: Tue, 15 Dec 2020 22:41:42 +0100	[thread overview]
Message-ID: <3b90b261-7920-671a-6566-70cd97b8d0e4@gmail.com> (raw)
In-Reply-To: <CAP8UFD2ibGdznacrC=Sf6pZtzEiGJ7v+2L8PbM3m2PDdSBoYYg@mail.gmail.com>

Hello Christian.

On 13.12.2020 11:10, Christian Couder wrote:
> Hi,
> 
> On Fri, Dec 11, 2020 at 3:07 PM Miłosz Kosobucki <mikom3@gmail.com> wrote:
> 
> I have been playing a bit with partial clone (see
> https://lore.kernel.org/git/CAP8UFD35kk10FpUnPpiAUzTHJbm=SJ-76OTmkTwBstGFe3Zgdw@mail.gmail.com/),
> and I started working on `git repack` and the underlying `git
> pack-objects`, so that `git repack -a -d --filter=...` could work. I
> cannot promise anything about when it will be submitted, merged,
> released, etc.
> 
> Also I have been working on it on the server side though, where it's
> ok to get rid of everything that is stored elsewhere. It might not be
> your case, but on the client side one might want to keep the (large)
> blobs that can be reached directly from the tip of some branches,
> which might require further work.
> 
>> 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,
> Christian.
> 

Thank you very much for this detailed information, and thanks for all 
the great work you and the git community are doing.

Best,
-- 
Miłosz Kosobucki

      reply	other threads:[~2020-12-15 21:44 UTC|newest]

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

  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=3b90b261-7920-671a-6566-70cd97b8d0e4@gmail.com \
    --to=mikom3@gmail.com \
    --cc=christian.couder@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).