Re: [oll-user] Git workflow
Resources for LilyPond and LaTeX users writing (about) music
Status: Alpha
Brought to you by:
u-li-1973
From: Phil H. <ma...@ph...> - 2014-01-11 11:56:24
|
----- Original Message ----- From: "Urs Liska" <ul...@op...> To: "Phil Holmes" <ma...@ph...>; <ope...@li...> Sent: Saturday, January 11, 2014 11:35 AM Subject: Re: [oll-user] Git workflow > > > Phil Holmes <ma...@ph...> schrieb: >>----- Original Message ----- >>From: "Urs Liska" <ul...@op...> >>To: <ope...@li...> >>Sent: Friday, January 10, 2014 9:58 PM >>Subject: Re: [oll-user] Git workflow >>> >>> Hm, just to be precise: you're not forking a branch but a repository. >>> That is: you have forked the complete repository, which contains all >>> branches. >>> Maybe that's what you meant, I just think these issues have to be >>clear. >> >>If I look at my git repo, it appears to be a snapshot when I forked it >>and >>doesn't contain the later branch. > > Yes, that's the way it works. > >> I therefore can't checkout the >>Schumann >>branch. How do I fix that? > > Assuming you have the fork as the "origin" and the main repo as the > "upstream" remote you can > > git fetch upstream > I obviously don't: $ git fetch upstream fatal: 'upstream' does not appear to be a git repository fatal: The remote end hung up unexpectedly How do I set your repo as upstream? -- Phil Holmes |