Fossil SCM
Request cmd line return 1 if no files updated, 2 for errors
f35bb2003cc81e6…
· opened 16 years, 1 month ago
- Type
- Feature_Request
- Priority
- —
- Severity
- Minor
- Resolution
- Wont_Fix
- Subsystem
- —
- Created
- March 7, 2010 10:58 a.m.
As it currently works, Fossil returns '0' on any command which succeeded, or '1' if the command was unknown or ambiguous.
It would be useful to be able to differentiate between 'no files were updated' and 'there was an error' in scripts. Therefore I would like to request that "0" be returned when 'all is well', '1' when 'upd' or other command updated files on disk (adding, removing or updating), and '2' if there was a problem understanding the command. Perhaps '3' if the command actually failed but was understood.
Comments (1)
The command dispatching mechanism does not really allow for this level of result code reporting. Implementing this would require touching a huge number of commands to make them consistent in this regard, and then documenting the result codes for each of them, then committing to retain those result codes for the lifetime of this project.