## on monty (my laptop)
I wonder why a "pull" doesn't just init a repo like a "svn co" does?
+Ah, I should have used `git-clone ssh://si.dabase.com/home/hendry/wikiwc/.git/`
monty:~/git-testing% git-init
Initialized empty Git repository in .git/
+You might want to set some config variables like your email as this [tutorial](http://www.kernel.org/pub/software/scm/git/docs/tutorial.html) describes.
+
monty:~/git-testing% git-pull ssh://si.dabase.com/home/hendry/wikiwc/.git/
warning: no common commits
remote: Generating pack...
Created commit d3507df: added test
1 files changed, 1 insertions(+), 0 deletions(-)
+I should have used `git push origin` here...
+
monty:~/git-testing% git-push ssh://si.dabase.com/home/hendry/wikiwc/.git/
updating 'refs/heads/master'
from 75a4a8e94e5fff2a4beced1574e772742d3f9847
hendry:242$ git-checkout master usb.mdwn
+I find this a little odd... Is this a required step for ikiwiki?
# Stuff I am confused about
* this master/origin stuff
-* why do I have to explicitly say the filename "usb.mdwn" for it to be updated?
\ No newline at end of file
+* why do I have to explicitly say the filename "usb.mdwn" for it to be updated?
+* how ikiwiki interfaces with git. does it have its own working copy? or is it the files simply in ~/wikiwc?
+* I know git-push seems unpopular (git-pull seems to have the emphasis), though I think it is really convenient
+
+# Ack
+
+Thanks to gitte on #git on Freenode
\ No newline at end of file