diff --git a/mindstab.net_blog/Mindstab.net_Guide_to_Setting_up_a_Git_Server.md b/mindstab.net_blog/Mindstab.net_Guide_to_Setting_up_a_Git_Server.md
index c03c6be..1eb05ff 100644
--- a/mindstab.net_blog/Mindstab.net_Guide_to_Setting_up_a_Git_Server.md
+++ b/mindstab.net_blog/Mindstab.net_Guide_to_Setting_up_a_Git_Server.md
@@ -12,6 +12,7 @@ I've found documentation on the setup of git servers and public repositories kin
     2. [Remote Repository For Public Access (git://)](#git.2.2)
     3. [Shared Multi-Developer Public Repository](#git.2.3)
 3. [Managing Multiple Developers, Repositories and Branches](#git.3)
+4. [Comments](#comments)
 
 [References](#git.ref)
 
@@ -177,6 +178,21 @@ The proper way to use git with multiple developers is for each developer to have
 
 *Note: I know this is the proper way but I haven't really had any experience with it, so until I get time to play with it unfortunately this part of the document will be empty.  Check out the official git manual for a good idea of how this should be managed, especially chapter 4 [Sharing Development](http://www.kernel.org/pub/software/scm/git/docs/user-manual.html#sharing-development)*.
 
+<a name="comments"></a>
+## Comments ##
+** Anon posted on 2010 10 **
+
+Section 2.3:
+
+    root@server # chmod g+ws proj -R
+
+this makes all files setgid when i think you really only wanted directories to be g+s
+
+    root@server # find proj -type f -print0 | xargs -0 chmod g+w
+    root@server # find proj -type d -print0 | xargs -0 chmod g+ws
+
+is probably better…
+
 <a name="git.ref"></a>
 ## References ##