I've been digging in, and it looks like it's possible I completely misread it, and that this would -- even with our small repository -- immediately blow up our bandwidth quota. It seems that the "large files" bandwidth is monitored separately, and that we'd be counted against it on every clone on an LFS-enabled system. So I'm still digging in to understand and see if there's an alternate, but right now I'm having some serious second thoughts.
On Tue, Apr 14, 2020 at 8:02 AM Kacper Kowalik email@example.com wrote:
Hey! sounds like a good idea! I think I saw a couple of other projects doing that. LSST (or whatever their current name is :-) ) being one of them. Cheers, Kacper
On 4/13/20 4:00 PM, Matthew Turk wrote:
We're seeing a bit of churn in the answer-store directory. I'd like to use git-lfs to manage this so that we can keep going without bloating the repo *too* much. We're getting a bit of churn right now and every time it adds a couple megs to the repo -- the latest one I'm looking at adds 15 megs, and I'm reluctant to do that.
This would keep our repo size down but also not disrupt our "answer-store" directory contents.
Any objections to trying this out?
-Matt _______________________________________________ yt-dev mailing list -- firstname.lastname@example.org To unsubscribe send an email to email@example.com
yt-dev mailing list -- firstname.lastname@example.org To unsubscribe send an email to email@example.com