svn commit: samba-web r354 - in trunk/devel: .

[deryck at samba.org]

Author: deryck
Date: 2004-09-24 21:19:56 +0000 (Fri, 24 Sep 2004)
New Revision: 354

WebSVN: http://websvn.samba.org/websvn/changeset.php?rep=samba-web&path=/trunk/devel&rev=354&nolog=1

Log:

Fix link to "CIFS Royalty Free Agreement."

--deryck

Modified:
   trunk/devel/index.html


Changeset:
Modified: trunk/devel/index.html
===================================================================
--- trunk/devel/index.html	2004-09-24 21:15:36 UTC (rev 353)
+++ trunk/devel/index.html	2004-09-24 21:19:56 UTC (rev 354)
@@ -7,7 +7,7 @@
 
 <p>Very often, questions arise concerning future plans for Samba.  For example:  "What functionality will be included in the next stable release?"  "What are the differences between the various CVS and Subversion code branches?" And also, "How can I learn more, get involved, help, etc?"  The information on this page is provided to help answer those kinds of questions.</p>
 
-<blockquote><b>Important:</b> In order to avoid any potential licensing issues we also ask that anyone who has signed the <a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnkerb/html/cifs_license_agreement.asp">Microsoft CIFS Royalty Free Agreement</a> not submit patches to Samba, nor base patches on the referenced specification.  We ask, too, that patches submitted to Samba not infringe on any known patents.  Finally, as with all GPL work, the submitter should ensure that submitted patches do not conflict with any third-party copyright.</blockquote>
+<blockquote><b>Important:</b> In order to avoid any potential licensing issues we also ask that anyone who has signed the <a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cifs/protocol/royalty-free_cifs_technical_reference_license_agreement.asp">Microsoft CIFS Royalty Free Agreement</a> not submit patches to Samba, nor base patches on the referenced specification.  We ask, too, that patches submitted to Samba not infringe on any known patents.  Finally, as with all GPL work, the submitter should ensure that submitted patches do not conflict with any third-party copyright.</blockquote>
 
 <h3>General Overview</h3>