From: Mathijs Kwik <mathijs@bluescreen303.nl>
To: git@vger.kernel.org
Subject: still using `git pack-redundant` - alternatives?
Date: Fri, 11 Jun 2021 13:10:58 +0200 [thread overview]
Message-ID: <CAKvOHKAFXQwt4D8yUCCkf_TQL79mYaJ=KAKhtpDNTvHJFuX1NA@mail.gmail.com> (raw)
Hi,
I have some scripts for personal automation where I use git for
backups and file synchronisation between systems.
It uses some form of tiering where large files, older files, and files
no longer present in branch heads, move to slower networked storage
and get linked via the "alternates" mechanism.
Since repacks are too expensive most of the time, I use `git
pack-redundant --all --alt-odb` to clear out "local" packs which
contents have become available in an alternate.
So since pack-redundant is nominated for removal, I would like to know
if there are any alternatives for this type of book-keeping. Of course
I can use `git show-index` and `comm` to implement similar
functionality, but using built-in facilities is less error-prone and
more efficient most of the time.
Cheers,
Mathijs
next reply other threads:[~2021-06-11 11:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 11:10 Mathijs Kwik [this message]
2021-06-14 6:59 ` still using `git pack-redundant` - alternatives? Jeff King
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='CAKvOHKAFXQwt4D8yUCCkf_TQL79mYaJ=KAKhtpDNTvHJFuX1NA@mail.gmail.com' \
--to=mathijs@bluescreen303.nl \
--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.
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 NNTP newsgroup(s).