The following is a Bad Idea that I want documented.

I was trying to track a remote branch by using the branch name:
'origin/<foo>'.  This is wrong.  All I needed to do was checkout
<foo>, and 'git checkout would automatically use the remote branch,
creating a new tracking branch.

I will undo the changes in the next commit.


git-svn-id: file:///home/candide/src/0_Local_SVN_Repos/sh.scripts/trunk@2874 92e5ae4a-8afd-0310-8b33-eaebc6dd6768
- Roll back to r2869.
- Added bugfixes.
- 'git_patchpull' only tries to create "$branchName" if a remote
  version of it doesn't already exist.


git-svn-id: file:///home/candide/src/0_Local_SVN_Repos/sh.scripts/trunk@2875 92e5ae4a-8afd-0310-8b33-eaebc6dd6768
- 'utl_notaDirArg' now always prints out something.
- Added 'utl_notaGitRepo' [extension of 'utl_notaDirArg'].
- 'git_patchpull' no longer creates a branch automatically.  There's
  now an option for specifying the branch to pull the patch into, if
  you want to use one.
- New Command:  'git_subtree'
  + Numerous utility-functions added to support the 'git_subtree'
    wrapper.


git-svn-id: file:///home/candide/src/0_Local_SVN_Repos/sh.scripts/trunk@2876 92e5ae4a-8afd-0310-8b33-eaebc6dd6768
Merge branch 'master' of /home/candide/src/github/svn.tools.staging/sh.scripts