Closed oprypin closed 4 years ago
What's the holdup with this particular pull request (the last one)? 😅
I was waiting for CI to finish after I fixed the merge conflict. Not sure why the milestone was changed. It should be ready to merge right away. @bcardiff Anything holding this up?
I changed the milestone because v0.12.0 is released already, but the milestone was not closed. I created a vNext because I'm not sure the next is 0.12.1 or 0.13.0
Thanks @oprypin
to avoid relying on a shell to pipe into
tar
.Caveat:
git checkout
also updates the index in the repository, but that shouldn't be a problem here (is there even any index in a bare repo to start with?)This is part of work to bring 'shards' to Windows.