X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/a25b695dc28dbe04fe9179c7a785bb35bc4ce2bd..ab2f53b081f98f92a40bb782ae9a755d7f6e4f6d:/doc/news/moved_to_git/discussion.mdwn?ds=sidebyside

diff --git a/doc/news/moved_to_git/discussion.mdwn b/doc/news/moved_to_git/discussion.mdwn
index ff950bb3a..fcb7186b9 100644
--- a/doc/news/moved_to_git/discussion.mdwn
+++ b/doc/news/moved_to_git/discussion.mdwn
@@ -11,3 +11,33 @@ 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]]
+
+>> Haha, I've also forgotten Arch and Superversion and probably a lot of
+>> another exotic SCMs ;)
+>>
+>> OK, Ikiwiki is your project, so you're the boss here ;)
+>>
+>> BTW, what do you think about migration of Debian projects from
+>> [svn.debian.org](http://svn.debian.org/) to [git.debian.org](http://git.debian.org/)?
+>> Is a good idea to use a few SCM servers by Debian?
+>>
+>> --[[Paweł|ptecza]]
\ No newline at end of file