Skip to content

GitRunCommand exception can store stdout output too. #198

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
Merged
merged 1 commit into from
Nov 12, 2014
Merged

GitRunCommand exception can store stdout output too. #198

merged 1 commit into from
Nov 12, 2014

Conversation

folti
Copy link
Contributor

@folti folti commented Nov 5, 2014

Some git commands, like git merge outputs their problems onto stdout,
instead of stderr, which will be thrown away by the current setup. This
change allows the GitPython commands to store the stdout's value too,
in case of error.
@folti
GitRunCommand exception can store stdout output too.
48f5476 
Some git commands, like git merge outputs their problems onto stdout,
instead of stderr, which will be thrown away by the current setup. This
change allows the GitPython commands to store the stdout's value too,
in case of error.
@coveralls
Copy link

Coverage Status

Coverage decreased (-13.55%) when pulling 48f5476 on folti:0.3 into 27c577d on gitpython-developers:0.3.
@Byron
Copy link
Member

Byron commented Nov 12, 2014

Thank you !
Byron added a commit that referenced this pull request Nov 12, 2014
@Byron
Merge pull request #198 from folti/0.3
678821a 
GitRunCommand exception can store stdout output too.
@Byron Byron merged commit 678821a into gitpython-developers:0.3 Nov 12, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants
@folti @coveralls @Byron