Handle parsing merge commit messages with multiple TFS changeset ids
Handle parsing merge commit messages with multiple TFS changeset ids

The original code would null out currentCommit after parsing the FIRST changeset id in the
log message, and associate the null commit hash with any additional changeset ids in the message
for the same commit. This eventually leads to a null reference error when executing git commands
that require the hash.

The new code ignores all of the changeset ids in the commit message except for the last one, which
is the only one that matters.

jeremy-sylvis-tmg/git-tfs,hazzik/git-tfs,kgybels/git-tfs,allansson/git-tfs,codemerlin/git-tfs,guyboltonking/git-tfs,NathanLBCooper/git-tfs,irontoby/git-tfs,codemerlin/git-tfs,hazzik/git-tfs,modulexcite/git-tfs,codemerlin/git-tfs,adbre/git-tfs,allansson/git-tfs,TheoAndersen/git-tfs,irontoby/git-tfs,irontoby/git-tfs,adbre/git-tfs,bleissem/git-tfs,steveandpeggyb/Public,allansson/git-tfs,kgybels/git-tfs,hazzik/git-tfs,jeremy-sylvis-tmg/git-tfs,bleissem/git-tfs,NathanLBCooper/git-tfs,WolfVR/git-tfs,steveandpeggyb/Public,adbre/git-tfs,TheoAndersen/git-tfs,allansson/git-tfs,steveandpeggyb/Public,guyboltonking/git-tfs,git-tfs/git-tfs,pmiossec/git-tfs,hazzik/git-tfs,bleissem/git-tfs,TheoAndersen/git-tfs,jeremy-sylvis-tmg/git-tfs,modulexcite/git-tfs,guyboltonking/git-tfs,modulexcite/git-tfs,NathanLBCooper/git-tfs,WolfVR/git-tfs,vzabavnov/git-tfs,WolfVR/git-tfs,TheoAndersen/git-tfs,PKRoma/git-tfs,andyrooger/git-tfs,kgybels/git-tfs