These are chat archives for halide/Halide

3rd
Dec 2017
Andrew Adams
@abadams
Dec 03 2017 17:29
Rewriting history worked, but was a little weird
turns out it's impossible to change what commit a closed PR refers to
Which means the old commits are still in there, referenced by historical PRs
and it's also impossible to delete closed PRs
However, a git clone doesn't fetch all the old PRs as branches unless you use --mirror
So a fresh checkout is indeed 100M now
and we didn't actually lose any data, due to the old PRs retaining the old master
So I guess that's good
This is going to be a little stressful for the buildbots
They're seeing a whole bunch of new commit ids in the open PRs that need testing
It's the equivalent of adding one new commit to every open PR
Zalman Stern
@zvookin
Dec 03 2017 23:31
Is there anything we need to do with existing repos? Does git pull work or do we need to trash them and clone from scratch?
Andrew Adams
@abadams
Dec 03 2017 23:31
git pull is a bad idea
it'll merge the remote version of the branch into the local version, mixing together the two histories
I'd just trash them to be sure
Zalman Stern
@zvookin
Dec 03 2017 23:32
Nuke it from space. It's the only way to be sure.
Andrew Adams
@abadams
Dec 03 2017 23:32
There's probably a safe thing you can do involving rebasing directly on top of the remote equivalent
indeed