aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMattias Andrée <maandree@operamail.com>2013-08-22 22:48:52 +0200
committerMattias Andrée <maandree@operamail.com>2013-08-22 22:48:52 +0200
commit31b9e516b07bc2377367bfc06de91d0a5c336d5b (patch)
tree2ba833c1e8034faa3818eefa1ce52f96f1cac691
parentwildcards (diff)
downloadusing-git-31b9e516b07bc2377367bfc06de91d0a5c336d5b.tar.gz
using-git-31b9e516b07bc2377367bfc06de91d0a5c336d5b.tar.bz2
using-git-31b9e516b07bc2377367bfc06de91d0a5c336d5b.tar.xz
add readme
Signed-off-by: Mattias Andrée <maandree@operamail.com>
-rw-r--r--README25
1 files changed, 25 insertions, 0 deletions
diff --git a/README b/README
new file mode 100644
index 0000000..5855491
--- /dev/null
+++ b/README
@@ -0,0 +1,25 @@
+In lack of good git documentation and manuals, I started by own.
+
+It seems to be lack of well written manuals, and Git's online
+documention itself is atrocious. Will I do not except the writers
+to have taking any course in pedagogy or didactics, or even any
+practical experience, I at least exept the writters to try to
+keep those aspects in mind, but that does not seem to be the case.
+
+Documentation should first introduct the concept, then the
+implementation; that is, first how to get started, than what
+they are doing. In other words, first how to create a Git
+repository and the absolute essantials, than introduce Git
+itself. Not first taking about what Git is, readers want to
+read the chapters in their order, if they do not have anything
+specific in mind.
+
+Documentation should then give you breif documentation of everthing
+you need to know in the order of imporantance, then, iterator be
+more advanced.
+
+But one of the most important part is not to start with dangerous
+commands just because it is easier to be lazy them. Try to do it
+right from the beginning, otherwise the wrong way will stick in
+the reader's memory.
+