Bugfixes to the 'git_subtree_add' mechanism:
- Prior to the 'git subtree add' call, we needed to perform a 'git
  status', for some reason.  Without it, the 'git subtree add'
  complains about a working-tree not being modified.
  .
  I don't know why.  Maybe the former command was being run too soon
  after the 'git remote add' step, and Git got confused.  Regardless,
  running the 'git status -s' silently does nothing when there
  *really* *are* no modifications.  And if there are, the caller will
  see them.

- The "--srcRepos" arg needs to be converted to an absolute-path
  *early*, before any 'pushd' calls.
  .
  The abs-path conversion code was also kinda broken.

- The name of the "addCmdFile" wasn't robust under subtree prefixes
  with a subpath.

- 'utl_gitSubtree_prefix2remote' and 'utl_gitSubtree_remote2prefix'
  were never really tested against prefixes with a subpath.

- The error message in 'utl_gitConfig_restorable' was incomplete and
  cryptic.

- 'utl_gitConfig_restorable' wasn't using the '--get-regexp' option
  correctly.

- Enhanced some other usage and error messages.


git-svn-id: file:///home/candide/src/0_Local_SVN_Repos/sh.scripts/trunk@2895 92e5ae4a-8afd-0310-8b33-eaebc6dd6768
- Bugfixes in 'utl_gitConfig_restorable'.


git-svn-id: file:///home/candide/src/0_Local_SVN_Repos/sh.scripts/trunk@2896 92e5ae4a-8afd-0310-8b33-eaebc6dd6768
Updating subtree "subtree._sh.scripts" from upstream.