Re: [Gcl-devel] Build issue

[Donald Winiecki]

On Fri, Oct 18, 2013 at 6:44 PM, Blake McBride <address@hidden> wrote:
> Please see question at the bottom.
>
>
>     git checkout Version_2_6_10pre
>
> works, but interestingly,
>
> address@hidden ~/Backup/gcl/gcl.git $ git pull
> Already up-to-date.
> address@hidden ~/Backup/gcl/gcl.git $ git branch
> * master
> address@hidden ~/Backup/gcl/gcl.git $ git checkout Version_2_6_10pre
> Branch Version_2_6_10pre set up to track remote branch Version_2_6_10pre
> from origin.
> Switched to a new branch 'Version_2_6_10pre'
> address@hidden ~/Backup/gcl/gcl.git $ git branch
> * Version_2_6_10pre
>   master
> address@hidden ~/Backup/gcl/gcl.git $ git checkout master
> Switched to branch 'master'
> address@hidden ~/Backup/gcl/gcl.git $ git branch
>   Version_2_6_10pre
> * master
> address@hidden ~/Backup/gcl/gcl.git $ git --version
> git version 1.7.10.4
>
>
> The first time I did a 'git branch' it only showed master.  Then, when I
> switch to a branch that I magically know about, git then knows about the
> branch.  Is there some sort of logic to this?  I don't get git because it
> defies any kind of understanding I try to apply to it.
>
> I know the world is nuts about git, and I'd really like to use it in a few
> circumstances, but I just can't seem to get it.  Your comments are greatly
> appreciated.
>
> Blake McBride
>

Hi Blake,

I think you'll find some satisfaction here --> http://gitref.org/branching/

>From this, I think you'll want `git checkout ...' rather than `git
branch' for the current tasks...

Best,

_don