Re: [fossil-users] git LFS
If you don't want to pollute your fossil repository with LBFs, you could use a similar approach to git's lfs solution by storing the actual files in Dropbox or boar (https://bitbucket.org/mats_ekberg/boar/wiki/Home) and text-linking to them from within your fossil-managed repo. I haven't tried either approach yet, but it seems feasible. On 28 October 2015 at 05:24, Joerg Sonnenberger wrote: > On Tue, Oct 27, 2015 at 05:01:09PM -0400, Ron W wrote: > > On Tue, Oct 27, 2015 at 4:29 PM, Abilio Marques > wrote: > > ... > > > > > As far as I can see, binary files get uploaded into a web server using > > > PUT, and then a reference is made into the repo. That way git doesn't > deal > > > with useless DIFFs of such files. Then, when a checkout is made, it > > > downloads the file over http/https. Seems like a neat solution. > > > > > > I guess that fossil users with a bunch of local repos (like myself) > > > wouldn't benefit if they had to load a web server. But for other > people, > > > perhaps... Perhaps if instead of a web server, the file just gets > copied in > > > a directory... I don't know... > > > > > > > Fossil's internal diffing algorithm handles binary files quite well. > Also, > > I recall reading somewhere that Fossil is able to determine when just > > storing the new content would be more efficient. > > Same for git really. > > Joerg > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] git LFS
On Tue, Oct 27, 2015 at 05:01:09PM -0400, Ron W wrote: > On Tue, Oct 27, 2015 at 4:29 PM, Abilio Marques wrote: > ... > > > As far as I can see, binary files get uploaded into a web server using > > PUT, and then a reference is made into the repo. That way git doesn't deal > > with useless DIFFs of such files. Then, when a checkout is made, it > > downloads the file over http/https. Seems like a neat solution. > > > > I guess that fossil users with a bunch of local repos (like myself) > > wouldn't benefit if they had to load a web server. But for other people, > > perhaps... Perhaps if instead of a web server, the file just gets copied in > > a directory... I don't know... > > > > Fossil's internal diffing algorithm handles binary files quite well. Also, > I recall reading somewhere that Fossil is able to determine when just > storing the new content would be more efficient. Same for git really. Joerg ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] git LFS
On Tue, Oct 27, 2015 at 4:29 PM, Abilio Marques wrote: ... > As far as I can see, binary files get uploaded into a web server using > PUT, and then a reference is made into the repo. That way git doesn't deal > with useless DIFFs of such files. Then, when a checkout is made, it > downloads the file over http/https. Seems like a neat solution. > > I guess that fossil users with a bunch of local repos (like myself) > wouldn't benefit if they had to load a web server. But for other people, > perhaps... Perhaps if instead of a web server, the file just gets copied in > a directory... I don't know... > Fossil's internal diffing algorithm handles binary files quite well. Also, I recall reading somewhere that Fossil is able to determine when just storing the new content would be more efficient. If you are curious about how Fossil encodes differences, see http://fossil-scm.org/index.html/doc/trunk/www/delta_format.wiki ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] git LFS
Yeah, I know, this is about fossil, but I want to mention this, at it seems an useful idea for people who uses binary files all the time. https://git-lfs.github.com/ As far as I can see, binary files get uploaded into a web server using PUT, and then a reference is made into the repo. That way git doesn't deal with useless DIFFs of such files. Then, when a checkout is made, it downloads the file over http/https. Seems like a neat solution. I guess that fossil users with a bunch of local repos (like myself) wouldn't benefit if they had to load a web server. But for other people, perhaps... Perhaps if instead of a web server, the file just gets copied in a directory... I don't know... Anyways, this is just in case anyone wanted to check it out, and make comments. If its an useful idea, count me in with help for the implementation. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
