io.EOF error opening raw objects about gogit

[TheDahv]

FWIW, here's where I went to read up about the EOF error and how consumers of Readers are supposed to deal with them:

• io.Reader
• io.EOF

There are other functions that return the contents of the file--though, perhaps not as efficiently as what you may be trying to do with your fixed-length buffer--that hide the EOF details away from the client code. I don't have as much familiarity with what other needs are met by this function, so I couldn't recommend either way.

[pgundlach]

I'll have a look, but unfortunately I won't be able to answer until the day after tomorrow.

[TheDahv]

No rush! This supports a side project for me, and I was happy to find a solution that didn't involve cgo. Kudos for the work done so far!

I offer a patch in case it is helpful: #9

This is a fun side project and has taught me a lot about git internals so far. Ideally the goal would be to have an easy binary that helps people new to a project find ideal reviewers for a pull request when they are new to a project.

Not to get too off topic, but have you thought about exploring implementations of git-blame or git-annotate? I'm having to do that by calling out to git for now.

[pgundlach]

Actually I don't do active development on this git project at the moment, so I don't have any plans to implement git-blame or git-annotate.

This repository was started to be good enough for another project (a rsync-git mirror at https://ctanmirror.speedata.de/2016-09-14/ which is currently 400 gigabyte)

[TheDahv]

Oh! I see you closed the issue. Is that to communicate that this project isn't supported and the fix won't be considered?

[pgundlach]

No, not at all. I thought the issue was fixed with the pull request (#9). I have included that pull request, so I am done (<-- at least, this is what I tought).

[TheDahv]

Oops, I misread and didn't see that. Ha, I didn't expect it to get merged so fast.

Thank you :)