The repo still grows and grows with every commit of a binary file. I don't fully understand this definition?
binary-glob --> The VALUE is a comma or newline-separated list of (versionable) GLOB patterns that should be treated as binary files for committing and merging purposes. Example: *.jpg ​Adding *.pdf to the above list means what exactly in terms of repo storage? On Tue, Jul 28, 2015 at 6:50 PM, Christopher M. Fuhrman <cfuhr...@pobox.com> wrote: > Howdy, > > On Tue, 28 Jul 2015 at 3:43pm, Paolo Bolzoni wrote: > > > Dear list, > > > > I am writing a pdf document using LaTeX, since some of the readers > > have problems compiling I'd like to keep also the .pdf under revision > > control. > > > > The .pdf is actually a binary output of other files, so it should be > > ignored during merge conflicts. I know this violated the basics of a > > scm, but it is possible to tell the repository to treat some file > > differently and do not try to merge them, but simply replace? > > I believe doing this: > > $ fossil settings binary-glob "*.pdf" > > would work. Probably better to do it from the web ui in case there are > other values present in that setting. > > Cheers! > > > > > Your faithfully, > > Paolo > > _______________________________________________ > > fossil-users mailing list > > fossil-users@lists.fossil-scm.org > > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > > > -- > Christopher M. Fuhrman > cfuhr...@pobox.com > > > _______________________________________________ > 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
