So, it turns out that this was a problem with a GREP_OPTION that I had
set.  I saw this post:
http://osdir.com/ml/git/2009-05/msg02219.html

Which, says to change from:
export GREP_OPTIONS='--color=always'

to:
export GREP_OPTIONS='--color=auto'

All is now right with the world.

Kyle

On Dec 2, 11:33 am, mudphone <kyle...@gmail.com> wrote:
> I have a submodule in my master project, and I was working in a branch
> of the master project.  In this master project branch, I did the
> following:
>
> - went into the submodule dir
> - checked out a topic branch
> - did a pull to get the latest on this topic branch
> - went back to the root dir of the master project
> - did a git submodule add for the submodule dir (without training /)
>
> After this, all was fine.  But, when I try to switch my master project
> to an older branch, my git submodule update fails:
>
> $ git submodule update
> error: pathspec 'a4bb226053b9d7e803f37f1d9eb63d1b21869fd7' did not
> match any file(s) known to git.
> Unable to checkout 'a4bb226053b9d7e803f37f1d9eb63d1b21869fd7' in
> submodule path 'lib/clojure/capjure'
>
> Is this because I am working in two different branches in my submodule
> dir?
>
> i.e.
> master project (branch A) --> submodule (branch 1)
> master proejct (branch B) --> submodule (branch 2)
>
> Please note, that all branches and commits are on the central repo for
> the submodule.
>
> If I do a git checkout "sha" for the submodule, I can for the update
> manually.  This to me proves that commits are all there.
>
> I'm assuming my workflow is bad.  Can anyone tell me what I'm doing
> wrong?
>
> Thanks!
> Kyle

--

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-us...@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.


Reply via email to