Yootil 1.1.2 [Updated: 8th Dec, 2018] Nov 4, 2012 11:41:08 GMT -8
Post by Chris on Nov 4, 2012 11:41:08 GMT -8
Learning curve from SVN = not too terrible. The git designer intentionally made it different from SVN because he hated SVN.
The way to make the transition easiest is to use their GUI apps instead of the command line.
Anyways, my only reason behind using git is it makes it much easier (as in, push of a button easy) to allow other users to submit "pull requests" (their own modifications to our code) that we review and then can easily merge directly into our code base. That way you can limit those with no-review write access to you and me, but allow everyone else to submit their own "suggestions."
Anyways, I'm fine with SVN. No reason to not open source this, so Google Code maybe?
Am liking the idea of code reviewing, but not understanding how that is done when a project is public.
Am reading some stuff about it now, and also installed Git.
Here it is...
I'll give it a try and see. Not sure I get the whole push / pull thing. Seems like an extra step just to get my changes into the rep.
So if you were to commit something to that now, how do I apply your changes to the rep?
So, git is distributed source control, that's why there's a different between commit and push/pull. It also is better with branching.
For example, we have "master," the normal branch. Now say I want to rewrite the built in template parser for yootil (dunno if there is one.) I'd create a branch called something like: epic-parser-rewrite
Now, this has a different timeline of commits. I can write all my modifications there. Then, when I'm ready to go, I push my branch back to GitHub. I send you a pull request containing my branch. This will then show you my list of commits (why commit vs push is important), the diff on my files, and any other comments I wrote. When you're done reviewing it, you can just click "Merge request" and it'll automatically (if possible) merge it in.
Very simple. Other benefits: You can comment inline on code in GitHub, so we can add notes (i.e. why we did what) or ask questions (during a pull request/code review) to individual lines of code. Very useful tool.
I'll pull that now, make some small modification and submit a pull request. That'll help walk you through the process.