Skip to content

Make inability to deal with 'first commits' more obvious in the docs #384

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.

Sign up for GitHub

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

Jump to bottom
Open
Byron opened this issue Feb 14, 2016 · 0 comments
Open

Make inability to deal with 'first commits' more obvious in the docs #384

Byron opened this issue Feb 14, 2016 · 0 comments
Labels
help wanted

Comments

@Byron
Copy link
Member

Byron commented Feb 14, 2016

GitPython cannot gracefully handle the following situations:

  • empty repository
  • diffing of the first commit against the (implied) empty tree

It would be nice to make this more obvious in the first steps of the documentation, possibly even in the README file.

This issues was spawned from #379.
@Byron Byron added this to the v1.0.3 - Fixes milestone Feb 14, 2016
@Byron Byron modified the milestones: v2.0.0 - Features and Fixes, v2.0.1 - Bugfixes Apr 24, 2016
@Byron Byron modified the milestones: v2.0.9 - Bugfixes, v2.0.10 - Bugfixes, v2.1.0 - proper windows support, v2.1.0 - better windows support, v2.1.1 - Bugfixes Oct 16, 2016
@Byron Byron modified the milestones: v2.1.1 - Bugfixes, v2.1.2 - Bugfixes Dec 8, 2016
@Byron Byron modified the milestones: v2.1.2 - Bugfixes, v2.1.3 - Bugfixes Mar 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Byron @nvie