Permalink
Browse files

update the references to RubyGarden's VimRubySupport page

  • Loading branch information...
1 parent 2bde747 commit b17270787b1639550798af355634c68b59118a6b @dkearns dkearns committed Jul 15, 2008
Showing with 9 additions and 4 deletions.
  1. +5 −0 ChangeLog
  2. +1 −1 FAQ
  3. +1 −1 README
  4. +2 −2 etc/website/index.html
View
@@ -1,3 +1,8 @@
+2008-07-15 Doug Kearns <dougkearns@gmail.com>
+
+ * FAQ, README, etc/website/index.html: update the references to
+ RubyGarden's VimRubySupport page
+
2008-07-08 Doug Kearns <dougkearns@gmail.com>
* NEWS: begin updating for the pending release
View
2 FAQ
@@ -191,7 +191,7 @@ appropriate. Try creating these lines of code and hitting SHIFT-ENTER:
For other suggestions, search the web or look at: >
- http://rubygarden.org/ruby?VimRubySupport
+ http://www.rubygarden.org/Ruby/page/show/VimRubySupport
*vim-ruby-faq-X* How can I report a bug? *vim-ruby-bug-reporting*
View
2 README
@@ -46,7 +46,7 @@ How you get these files into Vim:
RubyForge is to get the latest version of them.
Understanding the configuration files:
- - See www.rubygarden.org/ruby?VimRubySupport
+ - See http://www.rubygarden.org/Ruby/page/show/VimRubySupport
- Email any one of us or ruby-talk if you want more information added to
this page.
View
@@ -32,7 +32,7 @@
</p>
<p>
Project page: <a href="http://www.rubyforge.org/projects/vim-ruby">http://www.rubyforge.org/projects/vim-ruby</a><br>
- Explanation: <a href="http://www.rubygarden.org/ruby?VimRubySupport">http://www.rubygarden.org/ruby?VimRubySupport</a>
+ Explanation: <a href="http://www.rubygarden.org/Ruby/page/show/VimRubySupport">http://www.rubygarden.org/Ruby/page/show/VimRubySupport</a>
</p>
<h2>
README
@@ -89,7 +89,7 @@
RubyForge is to get the latest version of them.
Understanding the configuration files:
- - See www.rubygarden.org/ruby?VimRubySupport
+ - See http://www.rubygarden.org/Ruby/page/show/VimRubySupport
- Email any one of us or ruby-talk if you want more information added to
this page.

0 comments on commit b172707

Please sign in to comment.