Huu you are correct. I left out something that is quite important. I am using bitbucket/github depending on the project. This fork is through their site. As far as I understand it, the benefit, besides easy pull requests, is also so you can push your local changes to a server-side repo without them being integrated back into the main code base. Then, if your hard drive or something goes bad, your local changes that have been pushed to your "fork" in the cloud are backed up. Am I correct in this understanding also?
To answer your question, yes I am using a hosting site, and I'm interested in the "other way" to avoid different repo names. Thanks, Greg -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
