summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorOwen Jacobson <owen.jacobson@grimoire.ca>2013-01-16 15:18:50 -0500
committerOwen Jacobson <owen.jacobson@grimoire.ca>2013-01-16 15:18:50 -0500
commit6cc8806d559f5ab884f6104a8dfdc6639e022258 (patch)
treed5e3ea5c5aa8d5af960dcb35a2904829f09fac54
parent3d896569309b5cd5df0821c57ee007809be89010 (diff)
Git: no guts, no glory.
-rw-r--r--wiki/git/survival.md7
1 files changed, 7 insertions, 0 deletions
diff --git a/wiki/git/survival.md b/wiki/git/survival.md
index e64273d..35ca572 100644
--- a/wiki/git/survival.md
+++ b/wiki/git/survival.md
@@ -3,6 +3,13 @@
I think the `git` UI is pretty awful, and encourages using Git in ways that
will screw you. Here are a few things I've picked up that have saved my bacon.
+* You will inevitably need to understand Git's "internals" to make use of it
+ as an SCM tool. Accept this early. If you think your SCM tool should not
+ expose you to so much plumbing, [don't](http://mercurial.selenic.com)
+ [use](http://bazaar.canonical.com) [Git](http://subversion.apache.org).
+ * Git weenies will claim that this plumbing is what gives Git all of its
+ extra power. This is true; it gives Git the power to get you out of
+ situations you wouldn't be in without Git.
* `git log --graph --decorate --oneline --color --all`
* Run `git fetch` habitually. Stale remote-tracking branches lead to sadness.
* `git push` and `git pull` are **not symmetric**. `git push`'s