{"push_id":1001137502,"size":1,"distinct_size":1,"ref":"refs/heads/jstarks/tarlayer","head":"0203d0ef6d263ca9610be029c1206b85e221a51c","before":"192862d6a920befbec47332075ad5a98f9f5b419","commits":[{"sha":"0203d0ef6d263ca9610be029c1206b85e221a51c","author":{"email":"4f08c47f7080d055a9777fa88698f74c617e54d1@microsoft.com","name":"John Starks"},"message":"Write Windows layer diffs to tar in standard format\n\nPreviously, Windows layer diffs were written using a Windows-internal\nformat based on the BackupRead/BackupWrite Win32 APIs. This caused\nproblems with tar-split and tarsum and led to performance problems\nin implementing methods such as DiffPath. It also was just an\nunnecessary differentiation point between Windows and Linux.\n\nWith this change, Windows layer diffs look much more like their\nLinux counterparts. They use AUFS-style whiteout files for files\nthat have been removed, and they encode all metadata directly in\nthe tar file.\n\nThe one limitation is that, right now, tar/archive does not provide\na way to extend the tar format to include Windows metadata (security\ndescriptors, file creation time, etc.). In this change, Windows\nmetadata is being written as POSIX xattrs, which is not correct.\nA followup change will encode Windows metadata as tar pax extension\nheaders.\n\nSigned-off-by: John Starks <jostarks@microsoft.com>","distinct":true,"url":"https://api.github.com/repos/Microsoft/docker/commits/0203d0ef6d263ca9610be029c1206b85e221a51c"}]}