summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorKris Maglione <maglione.k@gmail.com>2009-01-07 00:22:03 -0500
committerKris Maglione <maglione.k@gmail.com>2009-01-07 00:22:03 -0500
commit64f7bfae48570a18dd4986d7bf409dd0423045ab (patch)
treeb7eef6b2f924aa5dcf7259540ae327e1258bfe58 /HACKING
parent9dfd4ca94a9edc164c400a79667c2055dec74339 (diff)
downloadpentadactyl-64f7bfae48570a18dd4986d7bf409dd0423045ab.tar.gz
Comment on SCM section in HACKING
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING10
1 files changed, 9 insertions, 1 deletions
diff --git a/HACKING b/HACKING
index 57d5f947..85cc55c0 100644
--- a/HACKING
+++ b/HACKING
@@ -137,4 +137,12 @@ TODO: Document the existence of remote branches and discuss when and how
to be added to a new branch. Keep in mind that git is not the most
intuitive SCM.
-<!-- vim: set fdm=marker sw=4 ts=4 et ai: -->
+ I don't agree. git is about as intuitive as any other SCM, but,
+ regardless, it's by far one of the most popular. There are
+ countless git walkthroughs, FAQs, tips pages (not to mention 'git
+ help') that I don't see the need to duplicate them here. As for
+ branches, 'git branch' should be sufficient, and, if not, there's
+ a list on gitweb.
+ --Kris
+
+# vim: set fdm=marker sw=4 ts=4 et ai: