X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/b906e01f498fb7b42b11d60813640616f92445e3..e6a2f3ba6c205de7af4d53f64d353ee5c6795445:/doc/news/moved_to_git/discussion.mdwn

diff --git a/doc/news/moved_to_git/discussion.mdwn b/doc/news/moved_to_git/discussion.mdwn
index e59faa2eb..f7e5dcb2c 100644
--- a/doc/news/moved_to_git/discussion.mdwn
+++ b/doc/news/moved_to_git/discussion.mdwn
@@ -5,9 +5,29 @@ ikiwiki to Git. Are there only easier way to maintain and submit patches for
 ikiwiki? It's very interesting for me, because I know you are long-time Subversion
 user and very experienced with it.
 
-I know that Git is very "modern" SCM these days, but I don't understand the hype
+I know that Git is very "trendy" SCM these days, but I don't understand the hype
 about it. This's not only one distributed SCM on the free/open source world.
 Maybe that model of work is better for you, but then you can use also Darcs,
 Mercurial, Bazaar or SVK :)
 
 --[[Paweł|ptecza]]
+
+> You forgot monotoone. :-)
+> 
+> Of those, only mercurial monotone and git have support in ikiwiki, and the
+> git support seems most mature and is definitely used by the most sites.
+> 
+> I don't consider which rcs is used a permanant or particularly significant
+> decision. I switched to svn with the express idea that sometime (I figured
+> within 10 years, it turned out to be 3), there would be something better,
+> with excellent conversion tools from svn.
+> 
+> At the moment, I'm happy with git, and it's definitely useful to not have
+> to worry about who derserves commit access to ikiwiki, or about next summer's
+> [[soc]] students (if we participate again) having to go through the ad-hoc
+> mess this year's did to contribute.
+> 
+> Being able to git-am < doc/todo/patch.mdwn is also potentially pretty neat. ;-)
+> 
+> --[[Joey]]
+