aboutsummaryrefslogtreecommitdiff
path: root/doc/news/moved_to_git
diff options
context:
space:
mode:
authorJoey Hess <joey@wren.kitenet.net>2007-11-07 05:52:58 -0500
committerJoey Hess <joey@wren.kitenet.net>2007-11-07 05:52:58 -0500
commita25b695dc28dbe04fe9179c7a785bb35bc4ce2bd (patch)
tree925fafaa30d59fa1d072cd5bd6c98a113f90fa8a /doc/news/moved_to_git
parentb906e01f498fb7b42b11d60813640616f92445e3 (diff)
downloadikiwiki-a25b695dc28dbe04fe9179c7a785bb35bc4ce2bd.tar
ikiwiki-a25b695dc28dbe04fe9179c7a785bb35bc4ce2bd.tar.gz
web commit by http://ptecza.myopenid.com/: * I meant that Git is trendy
Diffstat (limited to 'doc/news/moved_to_git')
-rw-r--r--doc/news/moved_to_git/discussion.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/news/moved_to_git/discussion.mdwn b/doc/news/moved_to_git/discussion.mdwn
index e59faa2eb..ff950bb3a 100644
--- a/doc/news/moved_to_git/discussion.mdwn
+++ b/doc/news/moved_to_git/discussion.mdwn
@@ -5,7 +5,7 @@ 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 :)