| |
| ▲ | mdaniel 4 days ago | parent | next [-] | | It by default doesn't allow any binaries at all, nor CRLF files <https://fossil-scm.org/home/help?cmd=commit#:~:text=may%20be...>, nor whatever default value it has for "oversized" That said, to the best of my knowledge git-lfs operates upon stdin and stdout, like much of git, so I'd guess you could actually just commit the tracking file and manually run $(git-lfs scrub) et al. I do hear that "manually run" isn't the same as the way it works in git, but that's why fossil does things the fossil way | | |
| ▲ | abc123abc123 3 days ago | parent [-] | | Incorrect. The whole sentence is: "may be aborted if a file contains content that appears to be binary, Unicode text, or text with CR/LF line endings unless the interactive user chooses to proceed. If there is no interactive user or these warnings should be skipped for some other reason, the --no-warnings option may be used." I use fossil and checking in binaries works beautifully. You _do_ get a warning, but as seen in the documentation, you can use --no-warnings if you don't want that. Note however, that you can't use diff on binaries, and since the entire history of the repository and the versions is shipped to all developers, storing large binaries quickly becomes cumbersome. I would in that case, store links to binaries, which themselves are stored in an archive, or switch to another scm program. | | |
| ▲ | amszmidt 3 days ago | parent [-] | | Note however, that you can't use diff on binaries, [...]
You absolutely can, but you need to use an external diff tool: fossil diff --command "compare"
You can also customise the diff-command variable. You might need to pass --diff-binary .. I forgot.As for storing binaries, unversioned files have no history, and are not synced automatically. |
|
| |
| ▲ | 3036e4 3 days ago | parent | prev | next [-] | | Not the same thing, but in addition to binary file support as mentioned in other comment, fossil supports adding unversioned files to the repository that are not version-managed at all. Might make sense for some large files if you just want it available but not versioned (only using space for the latest version) or automatically checked out. https://fossil-scm.org/home/doc/trunk/www/unvers.wiki | |
| ▲ | amszmidt 3 days ago | parent | prev [-] | | Yes, it is called "unversioned files" in Fossil, but the max size is limited to what SQLite can handle in a single blob (so ~4Gbytes) https://fossil-scm.org/home/doc/trunk/www/unvers.wiki |
|
