git notes main page | gitolite main page | license
IMPORTANT NOTE:
although this page has a "gitolite.com" URL, this is not about gitolite.
That's just an artifact of "sitaramc.github.com" being translated to
"gitolite.com" and so ALL my git related stuff gets carried over.
Gitolite documentation has another /gitolite in the URL, so
you can tell. My apologies for this confusion.
If you always wondered what exactly was meant by “commit-then-merge versus merge-then-commit”, take a couple of minutes to read https://www.ericsink.com/entries/dvcs_dag_1.html. You’ll also understand what a DAG (directed acyclic graph) is, in case you didn’t know, with very nice ilustrations at an easy reading pace.
This site belongs to someone who is making a commercial version control system, and is documenting his findings and thoughts very laboriously. While I don’t always agree with him, he (a) certainly writes well, and I absolutely love his sense of humour, and (b) is refreshingly honest about his biases in his followup blog post.
https://codeclimber.blogspot.com/2009/05/git-solves-all-your-branching-and.html talks about the reluctance to try branching when coming from a painful-to-branch model like SVN. The fact is, in git, branching is one of those rare beasts: easy and powerful.
https://www.lwn.net/Articles/381796/ Subversion is unable to separate the steps “fix bug A” and “integrate with bugfixes B C D and E, having been checked in while you’ve been working on A”. Mr. Corporate Manager wants this feature.
Subversion cannot do that unless you create a branch for everything. Poof your workflow is now an order of magnitude more complicated than git or hg (which is IMHO even less complicated than SVN, once you let go of the centralized-repo, poisoned-by-CVS mindset.)
about the best darn doc on using the 3 GUIs that come with git: https://nathanj.github.com/gitguide/tour.html has a Windows slant but except for the “installation” pieces, the rest is just as applicable to Linux
another very useful resource is the gitready site, where you’ll find lots of tips and techniques. In particular, they explain things very graphically (for example, if you always wondered what rebase is, try intro to rebase, then maybe pull with rebase or squashing commits with rebase).
release engineering, branches never-merged-back, etc., https://gitster.livejournal.com/2009/01/14/
Ingo Molnar (mingo) on reviewing merge commits versus rebased ones: https://lwn.net/Articles/409775/
Shawn on contrib/workdir/git-new-workdir: https://kerneltrap.org/mailarchive/git/2007/10/11/335637
git am -3 worksa somewhat longer, more philosophical article on git: https://www.betaversion.org/~stefano/linotype/news/106/
on tracking content instead of files: https://marc.info/?l=git&m=116473016012824
a more detailed version of the same: https://article.gmane.org/gmane.comp.version-control.git/217
descriptive article on the advantages of a DVCS and speculative branching and low overhead repos and so on: https://griddlenoise.blogspot.com/2007/12/distributed-vcss-are-great-enablers-or.html
very informative comment on the advantages of a distributed system: https://weblogs.mozillazine.org/preed/2006/11/version_control_system_shootou.html#comment-486521
https://keithp.com/blogs/Repository_Formats_Matter/ – discusses git from a small project point of view; you can retain your central model even with git
on git being very liberal: https://tomayko.com/writings/the-thing-about-git
look, don’t expect too much praise for any of the other systems, except possibly Hg – and even that might be back-handed ;-)
…but also see the archived article on subversion for a lot more; SVN is the most used VCS in terms of what potential git users are currently using, so it has its own page.
data integrity issues in VSS: https://www.developsense.com/testing/VSSDefects.html
from https://martinfowler.com/bliki/VersionControlTools.html: Before I finish with those behind the threshold, I just want to say a few things about a particularly awful tool: Visual Source Safe, or as I call it: Visual Source Shredder. We see this less often now, thank goodness, but if you are using it we’d strongly suggest you get off it. Now. Not just is it a pain to use, I’ve heard too many tales of repository corruption to trust it with anything more valuable than foo.txt.
TFS rant https://developers.slashdot.org/comments.pl?sid=1872398&cid=34258672
Used to be very slow. Now it’s probably just slow :-)