tree e32c783272859cc485714b3e6ed66619b841e016
parent 089734fb5f1ccb2d273ba7880525e6dd9c7ad8dd
author Matt Centurion <92415360+MattCenturion@users.noreply.github.com> 1634218357 -0700
committer GitHub <noreply@github.com> 1634218357 -0400
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJhaDF1CRBK7hj4Ov3rIwAA7+IIABpNmeh4WSDKXkg1dYem1RW4
 m47baJ5vz+lVMq4Ntgl5WZmY/NVVz+l47ULcIEJGbH9GK4xTQymEBInSRQ/Zf0uU
 6hfRt3s8mLyWoXqlSYyQ/UGfN3hOsVWksSC8lcn8YuL742dsgjFK8aVx6A3ck0eA
 I/Ty1OGciV89/GTlXAhZFoRWWDodQlC1dJo3N+VWaLtnPfqRYL4xjuCmpodGssd1
 hMfFlq77YWFzV0el55c1MRzazXXAsGoTR/C5V9NFHe5jUOYnsIZ1NK45iGyTrOPK
 YY0GaIjjWFwE/61ew061CYfTqIfjToRESErXRTNHCP+T7YVGUDbOOO65StJUTe4=
 =v0Qh
 -----END PGP SIGNATURE-----
 

Correct read_dir nlink/blocks reporting (#540)

When requested via "--list --json" read_dir(...) loops thru AFCKeyValueRead(...) to obtain st_size/st_mtime/st_birthtime/st_nlink/st_blocks of each directory entry. Likely typo had st_nlink value being overwritten by st_blocks value causing reported "st_nlink" to match st_blocks and st_blocks always be "-1". Fix corrects this small typo and now both values are being reported correctly in this case.