Skip to content

FetchInfo.re_fetch_result has no reason to be public #649

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 28, 2017

Conversation

OddBloke
Copy link

And when using the API interactively, having it show up as public is
confusing.

And when using the API interactively, having it show up as public is
confusing.
@Byron
Copy link
Member

Byron commented Sep 28, 2017

Thanks a lot for your contribution, this makes total sense, and my apologies for getting to this PR that late!

@Byron Byron merged commit 2af601d into gitpython-developers:master Sep 28, 2017
@OddBloke OddBloke deleted the hide_re_fetch_result branch September 28, 2017 17:38
@OddBloke
Copy link
Author

Thanks @Byron!

riley-martine pushed a commit to riley-martine/GitPython that referenced this pull request Dec 7, 2023
…ch_result

FetchInfo.re_fetch_result has no reason to be public
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants