Fossil: View Ticket

2011-04-18
19:38		• Ticket [40a7d777a4] fossil up doesn't recover deleted file (fossil up -v does....) status still Fixed with 1 other change artifact: 8717720fb2 user: anonymous
18:25		• Fixed ticket [40a7d777a4]. artifact: a0c9ae7f1b user: drh
18:25		Make sure the "update" command always works the same with or without the -v option. Ticket [40a7d777a465]. check-in: e11513631f user: drh tags: trunk
16:29		• Ticket [40a7d777a4] fossil up doesn't recover deleted file (fossil up -v does....) status still Open with 2 other changes artifact: df015e1ea2 user: anonymous
16:27		• New ticket [40a7d777a4]. artifact: 0ae6fd9e93 user: anonymous

Ticket Hash:	40a7d777a46548727f3988ca26bbd824f1730813
Title:	fossil up doesn't recover deleted file (fossil up -v does....)
Status:	Fixed	Type:	Code_Defect
Severity:	Important	Priority:
Subsystem:		Resolution:	Fixed
Last Modified:	2011-04-18 19:38:59 15.01 years ago	Created:	2011-04-18 16:27:32 15.01 years ago
Version Found In:	cea065c7f2

Description:

if I delete one file from repository and I do a fossil up to recover it, it doesn't work (nothing happens). But fossil up -v recover the deleted file as expected...

Seems that "-v" does more than adding verbosity...

anonymous claiming to be Martin added on 2011-04-18 16:29:10 UTC:
Correction: When I say "Delete one file from repository", I mean Delete the file locally from file system..

drh added on 2011-04-18 18:25:49 UTC:
The problem with the -v switch has been fixed.

For restoring a deleted file, you want the "revert" command, not "update".

anonymous added on 2011-04-18 19:38:59 UTC:
Ok.. now -v does the same as without it.. but may be a bit too much, we got identical outpout now. Before, we got bunch of UNCHANGED: " lines for every file in the repository with "-v". The new version doesn't show that anymore. Was it intentional ?

Anyway, the UNCHANGED: lines was not very usefull for me.. But having the MISSING: and EDITED: lines with -v would be usefull (without the UNCHANGED ones)