From: Oleg Broytman <phd@phdru.name>
Date: Mon, 1 Jun 2015 20:54:03 +0000 (+0300)
Subject: Add draft chapters to be filled later
X-Git-Url: https://git.phdru.name/?a=commitdiff_plain;h=0d79759c6e1fbf3346b1511af03a76ff24191e65;hp=e2139e1184b1b1368d6134ff71de15de424c2da2;p=git-wiki.git

Add draft chapters to be filled later
---

diff --git a/pep-git.txt b/pep-git.txt
index 6ed8bba..5fe6565 100644
--- a/pep-git.txt
+++ b/pep-git.txt
@@ -200,6 +200,66 @@ already been pushed. Not a problem until commits are in a public
 repository.
 
 
+Undo
+====
+
+TODO: describe undo strategies: git reset, git revert, git checkout,
+git reflog. "Commit early, commit often".
+
+How to undo a merge
+https://kernel.org/pub/software/scm/git/docs/howto/revert-a-faulty-merge.html
+
+
+Advanced topics
+===============
+
+Staging area
+------------
+
+Staging area aka index is a distinguishing feature of git. See
+`WhatIsTheIndex
+<https://git.wiki.kernel.org/index.php/WhatIsTheIndex>`_ and
+`IndexCommandQuickref
+<https://git.wiki.kernel.org/index.php/IndexCommandQuickref>`_ in Git
+Wiki.
+
+
+Advanced configuration
+======================
+
+Line endings
+------------
+
+Git has builtin mechanisms to handle line endings.
+
+TODO: describe crlf configuration and .gitattributes.
+
+
+Null-merges
+===========
+
+Git has a builtin strategy for what Python core developers call
+"null-merge"::
+
+    $ git merge -s ours v1 # null-merge v1 into v2
+
+
+Database maintenance
+====================
+
+TODO: dangling objects, git gc, git repack.
+
+
+From Mercurial to git
+=====================
+
+Mercurial for Git users https://mercurial.selenic.com/wiki/GitConcepts
+
+https://github.com/felipec/git-remote-hg
+
+https://hg-git.github.io/
+
+
 References
 ==========