Author: deryck
Date: 2005-10-23 12:46:35 +0000 (Sun, 23 Oct 2005)
New Revision: 838

WebSVN: 
http://websvn.samba.org/cgi-bin/viewcvs.cgi?view=rev&root=samba-web&rev=838

Log:
Language change from"ask" to "require" based on 
suggestion from Dan Shearer.

deryck

Modified:
   trunk/devel/index.html


Changeset:
Modified: trunk/devel/index.html
===================================================================
--- trunk/devel/index.html      2005-10-20 17:13:05 UTC (rev 837)
+++ trunk/devel/index.html      2005-10-23 12:46:35 UTC (rev 838)
@@ -8,7 +8,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/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>
+<blockquote><b>Important:</b> In order to avoid any potential licensing issues 
we require 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 require, 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>
 

Reply via email to