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
eith
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
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 fi
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 gi
4 matches
Mail list logo