3 I'm very curious about the main reasons of your leaving Subversion and moving
4 ikiwiki to Git. Are there only easier way to maintain and submit patches for
5 ikiwiki? It's very interesting for me, because I know you are long-time Subversion
6 user and very experienced with it.
8 I know that Git is very "trendy" SCM these days, but I don't understand the hype
9 about it. This's not only one distributed SCM on the free/open source world.
10 Maybe that model of work is better for you, but then you can use also Darcs,
11 Mercurial, Bazaar or SVK :)
15 > You forgot monotoone. :-)
17 > Of those, only mercurial monotone and git have support in ikiwiki, and the
18 > git support seems most mature and is definitely used by the most sites.
20 > I don't consider which rcs is used a permanant or particularly significant
21 > decision. I switched to svn with the express idea that sometime (I figured
22 > within 10 years, it turned out to be 3), there would be something better,
23 > with excellent conversion tools from svn.
25 > At the moment, I'm happy with git, and it's definitely useful to not have
26 > to worry about who derserves commit access to ikiwiki, or about next summer's
27 > [[soc]] students (if we participate again) having to go through the ad-hoc
28 > mess this year's did to contribute.
30 > Being able to git-am < doc/todo/patch.mdwn is also potentially pretty neat. ;-)
34 >> Haha, I've also forgotten Arch and Superversion and probably a lot of
35 >> another exotic SCMs ;)
37 >> OK, Ikiwiki is your project, so you're the boss here ;)
39 >> BTW, what do you think about migration of Debian projects from
40 >> [svn.debian.org](http://svn.debian.org/) to [git.debian.org](http://git.debian.org/)?
41 >> Is a good idea to use a few SCM servers by Debian?
projects / ikiwiki / blob