On Fri, 24 May 2019 at 10:13, Jeff King <p...@peff.net> wrote: > It's possible Git is doing the wrong thing on the writing side, but > given that newer versions of bsdtar handle it fine, I'd guess that the > old one simply had problems consuming poorly formed symlink filenames.
I agree that the reader should be able to handle it best-effort. Especially given both bsdtar and gnutar seem to not choke on it. I mentioned go's archive/tar chokes on it, so reported that issue https://github.com/golang/go/issues/32264 -Keegan
