MinGW bash does not report negative exit status codes: http://sourceforge.net/tracker/?func=detail&atid=102435&aid=1172090&group_id=2435 Due to above when running git-tfs in a script in MinGW there's no way of knowing whether git-tfs operation was succesfull or failure caused by a thrown exception. Negative exit status codes are replaced with positive ones constraining them to Byte.MaxValue. This is so that the behavior of the program is consistent and predictable in all running environments (e.g. bash, cmd.exe, powershell.exe, zsh, sh). While cmd.exe and powershell.exe support exit status codes higher than 255, UNIX-like running environments only support values between 0 and 255: http://www.gnu.org/software/libc/manual/html_node/Exit-Status.html Signed-off-by: Tuomas Järvensivu <firstname.lastname@example.org>
…nControl.AuthorizedUser. The old version was returning '<Firstname> <Lastname>' which was throwing back an identity error when trying to fetch existing shelfsets
…breaking unshelve functionality
Oh, it's so fun to develop .NET without a windows machine...
tfs-remote.<id>.autotag option implemented. Defaults to false.
…tiple times if Changes property queried more then once.