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
The git-annex special remote protocol is somewhat unusual in that the last field of a line can contain whitespace, while all previous fields cannot. So, simply splitting by whitespace can result in more fields than expected, when there is in fact whitespace in the last field.
This is particularly a problem for TRANSFER, since the filename passed as its last field does contain whitespace in some edge cases. Note that the external special remote documentation used to incorrectly say it never contained whitespace.
The text was updated successfully, but these errors were encountered:
arcnmx
added a commit
to arcnmx/go-git-annex-external
that referenced
this issue
Feb 5, 2020
The git-annex special remote protocol is somewhat unusual in that the last field of a line can contain whitespace, while all previous fields cannot. So, simply splitting by whitespace can result in more fields than expected, when there is in fact whitespace in the last field.
This is particularly a problem for TRANSFER, since the filename passed as its last field does contain whitespace in some edge cases. Note that the external special remote documentation used to incorrectly say it never contained whitespace.
The text was updated successfully, but these errors were encountered: