You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for bringing this up! I have had cases where a fetch result was not correctly understood as well, and it seems one really wants to use regex here instead of parsing it manually.
Parsing needs to be more robust here and in some other cases.
It would be great to have a FETCH_HEAD example with an actual comment in it.
FETCH information parsing was improved a lot, and I wonder if this is still an issue.
Maybe you can provide more information helping to reproduce this, until I start working on 0.3.5.
Thank you.
As I am unable to reproduce this issue, I will close it, also referring to the large amount of changes that were introduced in the meanwhile.
If there is still an issue of this kind in the latest release, please file it.
When fetching a ref from a remote server, the ref file can contain a comment, like:
The file FETCH_HEAD:
ecc2505c5d373f8384477cc4d831bbd9323d061c 'refs/my/stuff' of git://my.git/my/repo.git
Because this comment is prefixed with two tabs, it breaks the value.split() call in SymbolicReference._get_ref_info().
The text was updated successfully, but these errors were encountered: