>From phone. Thank you everyone. I am finally github - able. Took large chunk of my day but it was worth it. Kind regards, Willem
On 17 Nov 2017 17:53, "Dirk Hohndel" <[email protected]> wrote: > On Nov 17, 2017, at 7:51 AM, Willem Ferguson < [email protected]> wrote: > > On 17/11/2017 17:38, Dirk Hohndel wrote: >> >> And just in case that isn't obvious - there really isn't a huge need to keep the 'master' in your fork in sync with upstream. You can always just pull from upstream on your local machine. > But I can only issue a PR from my fork on Github. Therefore my Github fork should contain an up-to-date master with my change that I wish to have pulled. Is this correct? Actually, GitHub doesn't care if YOUR master is up to date. If you push a branch on which you worked to GitHub, it will offer to you to create a PR against master of the upstream project which you forked. /D _______________________________________________ subsurface mailing list [email protected] http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
_______________________________________________ subsurface mailing list [email protected] http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
