| commit | 7e952e797c98fca1853463247bcaf3b8d58bc36c | |
| author | Paul Mackerras <paulus@samba.org> | |
| Mon, 27 Jun 2005 10:04:26 +0000 (27 20:04 +1000) | ||
| committer | Paul Mackerras <paulus@samba.org> | |
| Mon, 27 Jun 2005 10:04:26 +0000 (27 20:04 +1000) | ||
| tree | 149a6ef18a269ef8dbcf9df40886d1f637eae0e7 | treesnapshot (tar.gz zip) |
| parent | 74daedb62cd2aa0420ee7fac5180246508867679 | commitdiff |
Fix a bug where we would corrupt the stuff read from git-rev-list.
If we have a very long commit message, and we end up getting a
bufferfull of data from git-rev-list that all belongs to one commit,
we ended up throwing away the data from a previous read that should
have been included. The result was a error message about not being
able to parse the output of git-rev-list.
Also, if the git-rev-list output that we can't parse is long, only put
the first 80 chars in the error message. Otherwise we end up with an
enormous error window.
If we have a very long commit message, and we end up getting a
bufferfull of data from git-rev-list that all belongs to one commit,
we ended up throwing away the data from a previous read that should
have been included. The result was a error message about not being
able to parse the output of git-rev-list.
Also, if the git-rev-list output that we can't parse is long, only put
the first 80 chars in the error message. Otherwise we end up with an
enormous error window.
| gitk | diffblobblamehistory |