Chris McGee

Yes, it looks like it. Check indexpack.go around line 711. There's no case for tags.

@driusan in order to add tag support for index pack, is it just a matter of putting OBJ_TAG in the switch statement here or is there special processing needed for...

Unfortunately, it's not that simple. Now the fetch tests begin failing with an index out of bounds on indexpack.go:452 Where can one learn more about how the indexing format here...

After logging more information on this here is the HTTP response in question: ``` Unexpected status code for response: got 422 body: Oh no · GitHub body { background-color: #f1f1f1;...

Definition of HTTP response code 422: "The request was well-formed but was unable to be followed due to semantic errors." It looks like the proxy server didn't like something about...

Hmm, now I'm getting an error cloning that repo directly from GitHub while working on #149

Nm, It was just the check to switch to protocol v2.

My understanding is that this service was provided to work around the lack of go get versioning. I suspect that the service will be going away slowly now that there...

As soon as we get the modules working with dgit I will probably move ghfs away from using the gpkg.in service. Maybe we should just close this?

I'm thinking that we should close this now. Go has settled on modules for versioning dependencies.