Hi Dylan, On 4 June 2018 at 19:18, Dylan Baker <dy...@pnwbakers.com> wrote: > Quoting Daniel Stone (2018-06-03 13:19:51) >> One thing I've just remembered is that https://www.mesa3d.org/archive/ >> serves all the tarballs for Mesa releases. Given how Pages is >> structured, we don't have a good way to redirect these to the old >> server, so the Pages repository needs to hold all the tarballs. This >> probably suggests to me that the site should live in a different repo, >> where we can just commit all the tarballs. >> >> I reflexively didn't love the idea of committing tarballs to a git >> repository, but the more I think about it, the more I like the idea. >> It makes it more clear where they're coming from, makes the provenance >> easier to verify, gives us audit logs of who put them in, and so on. > > Have you considered git-lfs? I don't know if we've got it set up, but gitlab > supports it and it's pretty nice for dealing with repos with large binary > files.
Is git-lfs mainly about supporting large individual files, or large collections of relatively small files? The tarballs aren't massive, there are just tons of them. If it does seem like a good idea, I'll get it set up in our instance. Cheers, Daniel _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev