git-guide
git-guide copied to clipboard
rogerdudler
Never explained what "origin" is
Never really explain what "origin" is, but then go and use it in the Branching section. This is a rather unique term to GIT/DVC, so new people (maybe coming from SVN) will definitely get confused.
Hey Adam,
You're right, there is a section missing about "origin", remotes, etc. I'm not exactly sure how to explain it yet. You might have some hints?
Cheers Roger
On Mon, Jan 23, 2012 at 10:23 PM, Adam Harte [email protected] wrote:
Never really explain what "origin" is, but then go and use it in the Branching section. This is a rather unique term to GIT/DVC, so new people (maybe coming from SVN) will definitely get confused.
Reply to this email directly or view it on GitHub: https://github.com/rogerdudler/git-guide/issues/19
Blog: http://www.rogerdudler.com Twitter: rogerdudler Xing: https://www.xing.com/profile/Roger_Dudler Skype: rogerdudler GTalk: [email protected]
origin is simply the consensus handle for remote repositories, I rarely use origin, rather a mixture of "github", "work", "koolvin" etc. as sometimes you want two different remote repos attached to the same git directory.
One example is something like:
git remote add github [email protected]:blah/blah.git
git remote add gitorious [email protected]:blah/blah.git
Another is working with a forked repo, you can add the fork as fork and the main repo as main in order to keep your changes synced.
Unless you have the specific needs @Koolvin mentioned, I'd rather vote for the more popular origin and upstream. People are used to these words. Again, of course, it's still a personal choice.
I wonder how you can word the last posts into something easy on the brainz...
