Zeitpunkt Nutzer Delta Tröts TNR Titel Version maxTL Fr 05.07.2024 00:00:27 61.919 0 3.520.710 56,9 Fosstodon 4.2.10 500 Do 04.07.2024 00:00:52 61.919 +2 3.517.337 56,8 Fosstodon 4.2.9 500 Mi 03.07.2024 00:00:12 61.917 +2 3.513.906 56,8 Fosstodon 4.2.9 500 Di 02.07.2024 00:01:44 61.915 -2 3.510.479 56,7 Fosstodon 4.2.9 500 Mo 01.07.2024 00:00:33 61.917 0 3.507.420 56,6 Fosstodon 4.2.9 500 So 30.06.2024 00:00:34 61.917 +2 3.504.671 56,6 Fosstodon 4.2.9 500 Sa 29.06.2024 00:01:13 61.915 +2 3.501.982 56,6 Fosstodon 4.2.9 500 Fr 28.06.2024 00:01:07 61.913 +3 3.498.459 56,5 Fosstodon 4.2.9 500 Do 27.06.2024 00:00:32 61.910 0 3.495.444 56,5 Fosstodon 4.2.9 500 Mi 26.06.2024 00:00:07 61.910 0 3.494.703 56,4 Fosstodon 4.2.9 500
(@mort) · 05/2019 · Tröts: 1.550 · Folger: 171
Fr 05.07.2024 23:35
To everyone who has some familiarity with the #posix #pax / #tar file formats: have you ever seen the 'g' file entry type used in practice?
For context: pax specifies extended metadata, to support things like nanosecond precision timestamps and arbitrary length paths. To do this, it adds two entry types: 'x', which applies metadata to the next entry, and 'g', which applies it to *all* following entries. 'x' is used all over the place; is 'g' ever used in practice? If so, for what?
[Öffentlich] Antw.: 0 Wtrl.: 0 Fav.: 0