On Wednesday, July 20, 2022 4:02:12 PM CEST Neal Gompa wrote:
GitHub's implementation has issues where smudging can be broken when doing complex merges that have LFS objects touched.
I do not think that LFS is set into stone yet, and this kind of interaction should be tested. IMHO one of the advantage of LFS is that is a very simple protocol, that can behave very nice with OBS. For example, there is currently in the PoC a proxy in place that routes back to OBS for old tgz, avoiding duplication. Future commits can delegate into OBS or another LFS server from this point, without much notice from the users PoV. The dist-git / fedpkg idea was commented too. I personally do not like it. The point is a bit irrelevant, but as a developer, when I am using a model that is like the one in OBS (tarball, spec, changes and patches), I do not like the context switch that requires fedpkg to manage the tgz at a different level. In that regard "osc" is better, and with git-LFS there is a chance to replicate this experience using a mostly pure git model. In any case this should be stressed, validated and revisited.
The history is better than nothing because things like Git blame work reasonably okay.
+1 on this. -- SUSE Software Solutions Germany GmbH Frankenstrasse 146 90461 Nuremberg Germany Geschäftsführer: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman (HRB 36809, AG Nürnberg)