Fossil SCM
fossil should delete repository & journal files if 'fossil clone' is cancelled
Closed
2d1109c64025121…
· opened 15 years, 5 months ago
- Type
- Feature_Request
- Priority
- —
- Severity
- Minor
- Resolution
- Overcome_By_Events
- Subsystem
- —
- Created
- Nov. 5, 2010 7:16 a.m.
If one cancels 'fossil clone' half-way (using ^c), fossil keeps to-be-created repository file and journal file. It should delete them.
For other cases where fossil clone fails due to some reason, it may keep these files only if asked (through command-line arguments) for debug purpose.
drh added on 2010-11-05 09:55:41: Catching the SIGINT and performing cleanup would require signal handling which is easy enough to do on unix, but is rather more challenging on windows. So even if we do provide this enhancement, it would be a unix-only thing, I suspect.
Comments (1)
stephan
2 years, 2 months ago
Fossil recently got the ability to resume a cancelled clone, which wouldn't be possible if this were implemented.