Thanks for correcting my concerns!
On Thursday, May 4, 2017 at 8:52:02 PM UTC-7, Dave Cheney wrote: > > > > On Friday, 5 May 2017 13:37:26 UTC+10, st ov wrote: >> >> By "fork" I mean in the GItHub sense, the forking of original project >> *github.com/original/foo >> <http://github.com/original/foo>* through their console so that >> *github.com/me/foo >> <http://github.com/me/foo>* is created. >> >> And "clone" would be running "git clone >> https://github.com/original/foo.git"; on my local machine so I have a >> local copy of the original project. >> >> > Thank you for clarifying. > > >> Does it matter which I do first? >> > > No, the order does not matter. You can fork the project on github, then > check out the upstream in its original location, then push to your fork, or > you could checkout the upstream, fork it, then push to your fork. > > Some rename the remote from origin to upstream, and add their fork as the > origin. Each to their own. > > >> Is there a chance someone could push a commit between those two events >> that would cause me some headache? >> > > I guess, but this doesn't seem much different to forking any other github > repo. > > >> >> >> >> >> >> On Wednesday, May 3, 2017 at 10:40:26 PM UTC-7, Dave Cheney wrote: >>> >>> This discussion could get confusing if we're not clear about our terms. >>> Could you please describe what the terms cloned and forked mean to you. >> >> -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
