From 3ddce6a96d843e7db7b2d76d7bfba69ab63b466c Mon Sep 17 00:00:00 2001
From: Michael Stack <stack@apache.org>
Date: Thu, 13 Sep 2012 22:35:25 +0000
Subject: [PATCH] Use link suggested by Otis

git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1384580 13f79535-47bb-0310-9956-ffa450edef68
---
 src/docbkx/community.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/docbkx/community.xml b/src/docbkx/community.xml
index 139e099681b..f4e47c38313 100644
--- a/src/docbkx/community.xml
+++ b/src/docbkx/community.xml
@@ -34,7 +34,7 @@
         <para>Feature Branches are easy to make.  You do not have to be a committer to make one.  Just request the name of your branch be added to JIRA up on the
         developer's mailing list and a committer will add it for you.  Thereafter you can file issues against your feature branch in HBase JIRA.  Your code you
         keep elsewhere -- it should be public so it can be observed -- and you can update dev mailing list on progress.   When the feature is ready for commit,
-        3 +1s from committers will get your feature merged<footnote><para>See <link xlink:href="http://search-hadoop.com/m/uPNz32C5FkS1&amp;subj=Re+Thoughts+about+large+feature+dev+branches">HBase, mail # dev - Thoughts about large feature dev branches</link></para></footnote>
+        3 +1s from committers will get your feature merged<footnote><para>See <link xlink:href="http://search-hadoop.com/m/asM982C5FkS1">HBase, mail # dev - Thoughts about large feature dev branches</link></para></footnote>
         </para>
       </section>         
     </section>