4 ms·
Fair. Note that this wasn't the only reason we had to fork. Go doesn't (or didn't) provide a way to pin to a dependency, so we would have had to fork anyway, a
by Manishearth 10y ago
Fair.
Note that this wasn't the only reason we had to fork. Go doesn't (or didn't) provide a way to pin to a dependency, so we would have had to fork anyway, and then rewrite all the paths anyway, so I went the way of using local paths in the fork.
- mixedCase 10y agoYou can probably consider unforking now that the vendor directory is a thing. I'm sure it'd be easier than rebasing on every update.