On September 11, 2013 06:08:05 PM Tim E. Real wrote:
> Whoa! Git is very weird in some respects.
> 
> Why must I clone a repo, giving me the master, then do a git 
> branch just to get to some branch?
   ^^^^^
Sorry, that and below, should read 'checkout'

> When I clone a repo, the file list (as viewed with a file manager) shows
>  one thing (the master). Then when I git 
>  branch to change to some branch,
   ^^^^^^                                       
  checkout

>  suddenly the file list shows something completely different (now the
>  branch instead of master).
> 
> Seems very odd, goes against all normalities of computing -  to have the
>  list of files suddenly change like that.
> 
> Why can't I just directly clone some branch I'm looking for?
> For that matter, why can't I clone all branches at once like with SVN?
> I like to have all branches on my system at once for reference or working
>  on several at the same time.
> 
> Seems to me novice users (like me, he he) would have a hard time
>  figuring out exactly how to get the branch they're looking for.
> There are no instructions for doing so on the host pages.
> 
> ---------
> Also, Flo I followed your instructions for transferring the origin,
>  as applied to my midi_engine_fixes branch, and now I suspect its
>  git config file is not correct:
> I pushed some small changes, and while the github repo did change
>  correctly, I got a denial error saying I was also trying to change master.
> I don't recall what my branch's git config file looked like before but
>  here is what it looks like now:
> (I'm currently using the recommended HTTPS, later I may go with SSH):
> 
> [core]
>       repositoryformatversion = 0
>       filemode = true
>       bare = false
>       logallrefupdates = true
> [branch "master"]
> [branch "midi_engine_fixes"]
> [remote "origin"]
>       url = https://[email protected]/muse-sequencer/muse.git
>       fetch = +refs/heads/*:refs/remotes/origin/*
> 
> Somehow I don't think that looks correct.
> Because here is what a test clone of our SF git repo looks like - even
>  after I did a 
>  'git branch' to arrive at my midi_engine_fixes branch:
            ^^^^^
           checkout

> [core]
>       repositoryformatversion = 0
>       filemode = true
>       bare = false
>       logallrefupdates = true
> [remote "origin"]
>       fetch = +refs/heads/*:refs/remotes/origin/*
>       url = https://[email protected]/p/lmuse/muse
> [branch "master"]
>       remote = origin
>       merge = refs/heads/master
> 
> Any suggestions for 'properly' correcting that first git config file?
> 
> Thanks.
> Tim.
> 


------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. Consolidate legacy IT systems to a single system of record for IT
2. Standardize and globalize service processes across IT
3. Implement zero-touch automation to replace manual, redundant tasks
http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
_______________________________________________
Lmuse-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmuse-developer

Reply via email to