Preparing Git-tf for publishing on Codeplex
Fixed 2 bugs:
- Clone reports one less cloned changeset than specified when using --depth
- Git-tf Configure/Checkin fails if the user tries to configure and checkin a git repo with more than one commit as shallow
Enhancing git tf checkin
- Added the ability to specify the checkin comment when checking in
  shallow using -m / --message
- Added the ability to preview what is going to be checked in TFS using -p
  / --preview
Added tags for all commits downloaded from TFS or checked in TFS to help
users identify commits synced to TFS
improved launcher experience when cmd.exe is not in the path
Updated the tag name for changesets downloaded to TFS_C[Number]
Merge branch 'master' of https://git01.codeplex.com/forks/ethomson/gittf into ethomson/gittf
Adding a couple of features to enhance access to what was downloaded to
tfs.
- Git tf now creates a remote tracking ref to what is in tfs in a remote
  branch called "origin/tfs"
- If the repo is a bare repo Git tf also creates a regular branch called
  "tfs" to unblock the bare repo scenario.1`
Updating the Major, Minor and Service Versions
Update the git-tf remote name to avoid confusion with origin
Updated clone and fetch test cases to verify that tags are created.
Rolling up commit's messages into a single comment if the user is checking in shallow and did not specify a checkin comment
Support for gated build triggering
Do not trigger a build if there are more than one affected gated builds
Updated CheckinPendingChangesTask to use the WorkspaceService instead of the workspace object when querying for the build service
Fixed bug#22 : Commit message used when --deep specified
- Added the ability to select a gated build definition to use if there are
multiple ones available.
- Added the ability to configure your repo to use that build definition by
  default every time.
Added Git Meta Data to TFS Changeset comments
Added a new parameter to enable turning on and off the git meta data when checking in deep
Fixed 2 bugs:
- [git-tf] checkin with invalid build defintion does not let the user know it is bad
- When checking in the "QueryItem" server call can be really expensive (optimized the call parameters)