|
2012-11-11
| ||
| 17:59 | • Fixed ticket [63cc656c9d]: Option to force binary file commits plus 2 other changes artifact: 3b3ab90688 user: drh | |
| 17:59 | Add the --binary-ok flag to the "fossil commit" command. Ticket [63cc656c9dfef126] check-in: 8c7faee6c5 user: drh tags: trunk | |
| 03:28 | • Ticket [63cc656c9d] Option to force binary file commits status still Open with 2 other changes artifact: ed0e077633 user: mistachkin | |
| 02:45 | • New ticket [63cc656c9d]. artifact: 90f6b44118 user: anonymous | |
| Ticket Hash: | 63cc656c9dfef126817a50e207f1170bb6f8b979 | ||
| Title: | Option to force binary file commits | ||
| Status: | Fixed | Type: | Feature_Request |
| Severity: | Important | Priority: | |
| Subsystem: | Resolution: | Fixed | |
| Last Modified: |
2012-11-11 17:59:43 13.55 years ago |
Created: |
2012-11-11 02:45:19 13.55 years ago |
| Version Found In: | current | ||
| Description: | ||||
|
I am writing a Windows-based GUI front-end to your excellent DVCS. My aim is to allow "ordinary" users the benefit of revision management on any file they choose. I also have selfish reasons as a developer to maintain local changes for my employment (we use Subversion).
My front-end calls FOSSIL.EXE to perform the work and is working beautifully for basic usage. However, when attempting to commit binary files I need a way to force the commit without having to answer this question: ./pic.png contains binary data. commit anyhow (a=all/y/N)? mistachkin added on 2012-11-11 03:28:58 UTC: | ||||