[SCM] Samba Website Repository - branch master updated

Andrew Bartlett abartlet at samba.org
Sat Jun 11 10:34:33 UTC 2016


The branch, master has been updated
       via  095fbef We use HTTPS now
       via  b2d4546 Remove outdated references to CVS, SVN and Binary_Packages
       via  735ea45 Remove trailing )
      from  53901b5 Clarify where mails to the security address go

https://git.samba.org/?p=samba-web.git;a=shortlog;h=master


- Log -----------------------------------------------------------------
commit 095fbef00e6e013f4e12bcc420ef5948ceb5e2a1
Author: Andrew Bartlett <abartlet at samba.org>
Date:   Sat Jun 11 22:29:13 2016 +1200

    We use HTTPS now

commit b2d4546c865146a6bea5f8c2caef556b5820c023
Author: Andrew Bartlett <abartlet at samba.org>
Date:   Sat Jun 11 22:26:29 2016 +1200

    Remove outdated references to CVS, SVN and Binary_Packages
    
    The Binary_Packages folder has not been updated in recent years

commit 735ea4521a70326436886eeab2780940e59e2f8c
Author: Andrew Bartlett <abartlet at samba.org>
Date:   Sat Jun 11 22:17:26 2016 +1200

    Remove trailing )

-----------------------------------------------------------------------

Summary of changes:
 contacts.html       |   3 +-
 cvs.html            | 156 ----------------------------------------------------
 download/index.html |  29 ++++------
 subversion.html     |  75 -------------------------
 4 files changed, 14 insertions(+), 249 deletions(-)
 delete mode 100755 cvs.html
 delete mode 100755 subversion.html


Changeset truncated at 500 lines:

diff --git a/contacts.html b/contacts.html
index 58f00f5..73834cf 100755
--- a/contacts.html
+++ b/contacts.html
@@ -13,7 +13,8 @@
   to <a href="mailto:security at samba.org">security at samba.org</a>
   <ul>
     <li>Mail to this address are private, sent only to
-      members of the <a href="team/">Samba Team</a>)</li>
+      members of the <a href="team/">Samba Team</a>
+    </li>
   </ul>
 <li>Discussing samba development in real-time: you might find a team member on the #samba-technical channel on the <a href="http://freenode.net/">http://freenode.net/</a> IRC server. Please DO NOT ask any user questions in #samba-technical, but in #samba instead!</li>
 </ul>
diff --git a/cvs.html b/cvs.html
deleted file mode 100755
index d100c9b..0000000
--- a/cvs.html
+++ /dev/null
@@ -1,156 +0,0 @@
-<!--#include virtual="/samba/header.html" --> 
-  <title>Samba - CVS Instructions</title>
-<!--#include virtual="/samba/header_columns.html" -->
-
-
-<h2 align="center">CVS Access to pserver.samba.org</h2>
-
-
-<H1>samba development changed to subversion</H1>
-
-In April 2004 Samba development changed from using CVS to Subversion for
-version control. Please see the <a href="/samba/subversion.html">subversion
-information</a> for details.
-
-<H2>Overview</H2>
-
-The machine pserver.samba.org runs a publicly accessible CVS
-repository for access to the source code of several packages.  This
-document describes how to get anonymous read-only access to this
-source code.
-
-
-<H3>Web access to the source</H3>
-
-<H4>Build Farm - Recent Checkins</H4>
-The Samba <a href="http://build.samba.org">build farm</a> provides access to the recent checkins on the
-<a href="http://build.samba.org/?&tree=samba_2_2&function=Recent+Checkins">samba_2_2</a>,  
-<a href="http://build.samba.org/?&tree=samba_3_0&function=Recent+Checkins">samba_3_0</a>
-and 
-<a href="http://build.samba.org/?&tree=samba&function=Recent+Checkins">HEAD</a>
-branches.. 
-
-<H4>CVSweb</H4>
-<p>You can access the source code via your favourite WWW browser. This
-allows you to access the contents of individual files in the
-repository and also to look at the revision history and commit logs of
-individual files. You can also ask for a diff listing between any two
-versions on the repository.</p>
-
-To access CVS via cvsweb click <A HREF="http://cvs.samba.org/cgi-bin/cvsweb/">here</A>.
-
-<H3>Access via cvs</H3>
-
-You can also access the source code via a normal cvs client. This
-gives you much more control over you can do with the repository and
-allows you to checkout whole source trees and keep them uptodate via
-normal cvs commands. This is the preferred method of access if you are
-a developer and not just a casual browser.<p>
-
-To gain access via anonymous cvs use the following steps. For this
-example I will assume that you want a copy of the samba source
-code. For the other source code repositories on this system just
-substitute the correct package name<p>
-
-<OL> 
-
-<LI> Install a recent copy of cvs. All you really need is a copy
-of the cvs client binary.</LI>
-
-<LI> run the command
-<blockquote><tt>
-	cvs -d :pserver:cvs at pserver.samba.org:/cvsroot login
-</tt></blockquote></LI>
-
-<LI> when it asks you for a password type <it>cvs</it> </LI>
-
-<LI> run the command 
-<blockquote><tt>
-	cvs -z5 -d :pserver:cvs at pserver.samba.org:/cvsroot co samba
-</tt></blockquote>
-
-This will create a directory called samba containing the latest samba
-source code.  This corresponds to the HEAD development branch.
-<p>
-If you want a different branch use the -r option to the co command to
-specify the branch. For example to checkout the SAMBA_2_2 branch run the
-command
-
-<blockquote><tt>
-	cvs -z5 -d :pserver:cvs at pserver.samba.org:/cvsroot co -r SAMBA_2_2 samba
-	  </tt></blockquote>
-If you want the latest 3.0 development code, use the SAMBA_3_0 tag.
-<blockquote><tt>
-        cvs -z5 -d :pserver:cvs at pserver.samba.org:/cvsroot co -r SAMBA_3_0 samba
-	  </tt></blockquote>
-
-
-</LI>
-
-<LI> Whenever you want to merge in the latest code changes use the following
-command from within the samba directory:
-<blockquote><tt>
-	cvs update -d -P
-	  </tt></blockquote>
-      </LI>
-
-</OL>
-
-NOTE: The Samba TNG project is now a separate development effort apart from
-the main Samba branch (not just another CVS code branch).  For the latest Samba
-TNG code, please refer to <a href="http://www.samba-tng.org/">http://www.samba-tng.org</a>.
-
-<h3>Converting from cvs.samba.org</h2>
-
-Anonymous access to the Samba cvs tree used to be via the host
-cvs.samba.org. That host is now reserved for developers with commit
-access and all anonymous access must be via pserver.samba.org.<p>
-
-If you have an existing checkout from cvs.samba.org then you can run
-the following script to convert the tree to use pserver.samba.org.
-<blockquote><tt>
-  find . -name Root -exec sh -c "sed 's/cvs\(.samba.org\)/pserver\1/g' < {} > {}. && mv {}. {}" \;
-</tt></blockquote>
-This command will change all occurances of cvs.samba.org to
-pserver.samba.org in the CVS/Root files in your tree.
-
-<H3>Access via rsync and ftp</H3>
-
-pserver.samba.org also exports unpacked copies of most parts of the CVS
-tree at <A
-HREF="ftp://pserver.samba.org/pub/unpacked">ftp://pserver.samba.org/pub/unpacked</A>
-and also via anonymous rsync at rsync://pserver.samba.org/ftp/unpacked/
-
-I recommend using rsync rather than ftp. See <A
-HREF="http://rsync.samba.org/">http://rsync.samba.org/</A>
-for more info on rsync.<p>
-
-The disadvantage of the unpacked trees is that they do not support
-automatic merging of local changes like CVS does. rsync access is
-most convenient for an initial install.
-
-<h3>Available branches</h3>
-
-<p>
-Please refer the <a href="/samba/devel/">Development and General Roadmap</a>
-page for information on the current cvs branches.
-
-<H3>How it's done</H3>
-
-If you are interested in how I have setup anonymous cvs access and
-want to set it up on your own system then you might like to checkout
-the pserver source code using the the command 
-<blockquote><tt>
-	cvs -d :pserver:cvs at pserver.samba.org:/cvsroot co pserver
-      </tt></blockquote>
-    
-You really have to know what you are doing to do this. Please don't
-mail me with basic cvs or unix security questions.
-
-<H2>Reporting problems</H2>
-
-If you have any problems with this system please ask on the <a
-href="http://lists.samba.org/">Samba mailing list</a>.
-
-
-<!--#include virtual="/samba/footer.html" -->
diff --git a/download/index.html b/download/index.html
index 22c7c45..0f66695 100755
--- a/download/index.html
+++ b/download/index.html
@@ -3,8 +3,8 @@
 <!--#include virtual="/samba/get_samba_menu.html" -->
 <h2>Download</h2>
 
-<p>The Samba source code is distributed via http.  View the download
-area <a href="/samba/ftp/">via HTTP</a>.  The file you probably want 
+<p>The Samba source code is distributed via https.  View the download
+area <a href="/samba/ftp/">via HTTPS</a>.  The file you probably want
 is called <a href="/samba/ftp/samba-latest.tar.gz">samba-latest.tar.gz</a>.
 Old releases are available in the <a href="/samba/ftp/old-versions/">Samba archives</a>.</p>
 
@@ -36,9 +36,9 @@ gpg: Good signature from "Samba Distribution Verification Key \
   <tr valign="top">
     <td>
       <h3 align="center">Binaries</h3>
-      Samba binaries are available for many popular platforms. You can download
-      them via http <a href="/samba/ftp/Binary_Packages">here</a>. Note 
-      that the latest version may not always be available for every platform.
+      All major Linux and Free Unix distributions have Samba as a native
+      package.  See your distributor's package or port system for a
+      native install of samba on your system.
 
       <p><a href="http://enterprisesamba.com/">http://enterprisesamba.com/</a>
       offers Samba packages for SLES, RHEL, and Debian.</p>
@@ -49,18 +49,13 @@ gpg: Good signature from "Samba Distribution Verification Key \
     <td>
     </td>
     <td>
-	<h3 align="center">Git, Subversion and CVS Sources</h3>
-          You can also fetch the sources using a source code control
-          system.  The advantage of fetching via a version control system 
-          that you can update your
-	  sources at any time using a single command.  See the <a 
-	  href="http://wiki.samba.org/index.php/Using_Git_for_Samba_Development">Git instructions</a>, <a 
-	  href="/samba/subversion.html">Subversion instructions (historical)</a> and <a 
-          href="/samba/cvs.html">CVS instructions (historical)</a> for information on 
-	  fetching the sources one of these tools.  Please be aware that the CVS and SVN
-          repositories are being maintained as archives only, and are not being 
-          updated.  Active development is only taking place within the Git
-	  repository. 
+	<h3 align="center">Git Sources</h3> You can also fetch the
+          sources using the <a href="http://git-scm.org">GIT source
+          code control system</a>.  The advantage of fetching via GIT
+          is can update your sources at any time using a single
+          command.  See
+          the <a href="http://wiki.samba.org/index.php/Using_Git_for_Samba_Development">Git
+          instructions</a>.
     </td>
   </tr>
   <tr valign="top">
diff --git a/subversion.html b/subversion.html
deleted file mode 100755
index a36a5a7..0000000
--- a/subversion.html
+++ /dev/null
@@ -1,75 +0,0 @@
-<!--#include virtual="/samba/header.html" --> 
-  <title>Samba - Subversion Instructions</title>
-<!--#include virtual="/samba/header_wide.html" -->
-
-<h2>Subversion access to svnanon.samba.org</h2>
-
-<H1>samba development changed to git</H1>
-
-In January 2008 Samba development changed from using Subversion to Git for
-version control. Please see the <a href="http://wiki.samba.org/index.php/Using_Git_for_Samba_Development">
-Using Git for Samba Development</a> for details.
-
-<h2>Overview</h2>
-
-<p>svnanon.samba.org contains an anonymous Subversion repository. The source 
-code in this repository is synchronised from the main branch every 5 minutes.</p>
-
-<p>Subversion is available from <a href="http://subversion.tigris.org/">subversion.tigris.org</a>.</p>
-
-<h3>Web access to the source</h3>
-
-<p>You can access the subversion repository via websvn at <a
-href="http://websvn.samba.org/">http://websvn.samba.org/</a>.</p>
-
-<h3>Access via subversion</h3>
-
-<p>To access the 'trunk', run:</p>
-
-<pre>
-svn co svn://svnanon.samba.org/samba/trunk samba-trunk
-</pre>
-
-<p>To check out a certain branch, say a branch called <b>BRANCH</b>, run:</p>
-
-<pre>
-svn co svn://svnanon.samba.org/samba/branches/<b>BRANCH</b> samba-<b>BRANCH</b>
-</pre>
-
-<p>Major current branches include:</p>
-
-<pre>
-svn co svn://svnanon.samba.org/samba/branches/SAMBA_3_0 samba-3_0
-</pre>
-<pre>
-svn co svn://svnanon.samba.org/samba/branches/SAMBA_4_0 samba-4_0
-</pre>
-
-
-<h3>Access via rsync and ftp</h3>
-
-<p>svnanon.samba.org also exports unpacked copies of most parts of the Subversion
-tree at <A
-HREF="ftp://svnanon.samba.org/pub/unpacked">ftp://svnanon.samba.org/pub/unpacked</A>
-and also via anonymous rsync at rsync://svnanon.samba.org/ftp/unpacked/</p>
-
-<p>I recommend using rsync rather than ftp. See <A
-HREF="http://rsync.samba.org/">http://rsync.samba.org/</A>
-for more info on rsync.</p>
-
-<p>The disadvantage of the unpacked trees is that they do not support
-automatic merging of local changes like CVS or Subversion does. rsync access is
-most convenient for an initial install.</p>
-
-<h3>Available branches</h3>
-
-<p>
-Please refer the <a href="/samba/devel/">Development and General Roadmap</a>
-page for information on the current cvs branches.</p>
-
-<h3>Reporting problems</h3>
-
-<p>If you have any problems with this system please ask on the <a
-href="http://lists.samba.org/">Samba mailing list</a>.</p>
-
-<!--#include virtual="/samba/footer.html" -->


-- 
Samba Website Repository



More information about the samba-cvs mailing list