Unix modification time in record: use the max of change and modify, not the min

pmeunier

Feb 27, 2023, 2:54 PM

QFXBAVXMCWV55XG3F4EGJP7PUCATRUHAARZWUZJRAZ7XLRARYIXQC

Dependencies

• [2] LEDABF7O Formatting
• [3] 7KNPYIDU Splitting the WorkingCopy trait into a read-only record and a read/write output
• [4] 2V33SO6I dont unwrap name() for RemoteRepo::LocalChannel
• [5] QU6T6J6W Use the change time in addition to the modified time when detecting untouched files (at least on Unix)
• [6] KGN7KVLA Formatting
• [7] 3ZAS64J6 Solving conflicts
• [8] Q6MRVSJX Higher resolution for status change times on Unix, and coarser test for 1-second-resolution filesystems
• [9] U56SMNHU Breaking out of potentially infinite loops in follow_oldest_path
• [*] SXEYMYF7 Fixing the bad changes in history (unfortunately, by rebooting).

Change contents

• replacement in libpijul/src/working_copy/filesystem.rs at line 393
  [3.87]→[3.383:423](∅→∅),[3.121]→[3.383:423](∅→∅),[2.200]→[3.383:423](∅→∅),[3.287]→[3.383:423](∅→∅),[3.350]→[3.383:423](∅→∅),[3.383]→[3.383:423](∅→∅)
  − Ok(attr.modified()?.min(ctime))
  [2.200]

  [3.423]
  + Ok(attr.modified()?.max(ctime))