You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openoffice.apache.org by bu...@apache.org on 2017/04/08 23:00:14 UTC
svn commit: r1010077 [23/31] - in /websites/staging/ooo-site/trunk: cgi-bin/
content/ content/pl/ content/pl/Archive/ content/pl/Archive/apps/
content/pl/Archive/apps/hr5000/ content/pl/Archive/grafika/
content/pl/Archive/info/ content/pl/Archive/marke...
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddSSHGuideTerminals.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddSSHGuideTerminals.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddSSHGuideTerminals.html.en Sat Apr 8 23:00:09 2017
@@ -0,0 +1,156 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-strict.dtd">
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+<style type="text/css">
+/* <![CDATA[ */ @import "/branding/css/tigris.css"; /* ]]> */
+</style>
+ <script src="/branding/scripts/sc.js" type="text/javascript"></script>
+ <link rel="stylesheet" type="text/css" href="/branding/css/print.css" media="print" />
+
+ <title>Using the desktop</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+ <div class="docs" id="ddsshguideterminals">
+ <h2>Using the Desktop Terminals</h2>
+
+ <div id="toc">
+ <ul>
+ <li><strong><a href="/nonav/servlets/HelpTOC">Help index</a></strong></li>
+ </ul>
+
+ <ul>
+ <li>
+ <a href="/nonav/docs/ddSSHGuide.html">About this guide</a>
+
+ <ul>
+ <li><a href="/nonav/docs/ddSSHGuide.html#aboutssh">About SSH</a></li>
+
+ <li><a href="/nonav/docs/ddSSHGuide.html#furtherdocumentation">Further documentation</a></li>
+ </ul>
+ </li>
+
+ <li><a href="/nonav/docs/ddSSHGuideConcepts.html">Concepts</a></li>
+
+ <li><a href="/nonav/docs/ddSSHGuideTerminals.html">Choosing the desktop terminal</a></li>
+
+ <li>
+ Using the Desktop Terminal
+
+ <ul>
+ <li><a href="#macs">Macintosh</a></li>
+
+ <li><a href="#windows">Windows</a></li>
+
+ <li><a href="#othersshclients">Other SSH clients</a></li>
+ </ul>
+ </li>
+
+ <li><a href="/nonav/docs/ddSSHGuideCygwin.html">Tunneling using Cygwin: The Desktop Unix Emulator</a></li>
+
+ <li><a href="/nonav/docs/ddSSHGuideterminating.html">Terminating the tunnel</a></li>
+ </ul>
+ </div>
+
+ <h3>Necessities</h3>
+
+ <dl>
+ <dt>Hostname</dt>
+
+ <dd><code>thisdomain.com</code></dd>
+
+ <dt>Local port:</dt>
+
+ <dd><code>2401</code></dd>
+
+ <dt>Remote port:</dt>
+
+ <dd><code>2401</code></dd>
+
+ <dt>Username:</dt>
+
+ <dd><code>tunnel</code></dd>
+
+ <dt>User password:</dt>
+
+ <dd><code>tunnel</code></dd>
+ </dl>
+
+ <h3><a id="macs" name="macs">Macintosh</a></h3>
+
+ <ul>
+ <li><a href="http://www.macssh.com">MacSSH</a></li>
+
+ <li><a href="http://www.lysator.liu.se/~jonasw/freeware/niftyssh/">NiftyTelnet SSH</a></li>
+ </ul>
+
+ <p>Both Mac clients offer intuitive interfaces; both also are well-documented. For that reason, this discussion of the Mac clients is very brief. However, for both clients, the important information is the same as for the Windows clients: the hostname and ports must be correctly specified.</p>
+
+ <h3><a id="windows" name="windows">Windows</a></h3>
+
+ <p>Two free clients for Windows provide SSH tunneling:</p>
+
+ <ul>
+ <li><a href="http://www.zip.com.au/~roca/ttssh.html">TTSSH</a>, an open-source add-on to Tera Term Pro</li>
+
+ <li><a href="http://www.chiark.greenend.org.uk/~sgtatham/putty/">PuTTY</a>, a free implementation of Telnet and SSH for Win32 platforms. It also provides an XTerm terminal emulator.</li>
+ </ul>
+
+ <p>As with the Mac clients, the important things to keep in mind are the hostname and the port numbers. For both terminals, the configuration process is straightforward. Because TTSH is an add-on to Tera Term, it means you have to go through that one extra step before SSH functionality is possible. [A fuller description of tunneling with TTSH is being drafted and will be posted when finished. For now, please see TTSH's <a href="http://www.zip.com.au/~roca/ttssh.html">website</a>.]</p>
+
+ <p>PuTTY, on the other hand, does not allow you to easily configure the client to handle port forwarding. As a result, it is not recommended for tunneling.</p>
+
+ <h3><a id="othersshclients" name="othersshclients">SecureCRT and F-Secure SSH</a></h3>
+
+ <p>Both these clients are fairly easy to use and configure for SSH1 tunneling. The information you will need--doubtless familiar by now--is listed below.</p>
+
+ <p>The following illustrates the procedure; we will use SecureCRT (version 3.1.2):</p>
+
+ <ol>
+ <li>Open a new session, specifying "SSH1" in the pull-down menu.</li>
+
+ <li>For "Hostname," enter "<code>thisdomain.com</code>."</li>
+
+ <li>Click on the "Advanced" button by "Hostname."</li>
+
+ <li>Once in the Advanced section, click on the "Port Forwarding" tab.</li>
+
+ <li>For "Local port," enter "<code>2401</code>."</li>
+
+ <li>For "Remote port" enter "<code>2401</code>."</li>
+
+ <li>For Username, enter "<code>tunnel</code>."</li>
+
+ <li>For User password, enter "<code>tunnel</code>."</li>
+
+ <li>For "Remote hostname," enter "<code>localhost</code>."</li>
+
+ <li>Enter "Save" and "OK" to exit the dialog box.</li>
+
+ <li>Back in the main connection page. . . .</li>
+
+ <li>Leave the defaults for "Cipher" and "Authentication" as they are.</li>
+
+ <li>Click on "Connect."</li>
+
+ <li>The server should then prompt for your password. It is "<code>tunnel</code>."</li>
+
+ <li>If this is your first time, the client will tell you that no "host key" for the server has been found and ask if you want to continue. Answer yes.</li>
+
+ <li>You are now tunneling.</li>
+
+ <li>The terminal screen does not show a prompt. That's how it should be. The tunnel has been established. You are now ready to begin using CVS securely.</li>
+ </ol>
+
+ <p>We discuss how to use the open-source desktop Unix emulator for Windows, Cygwin, in the section titled, <a href="/nonav/docs/ddSSHGuideCygwin.html">Tunneling using Cygwin</a>. Because Cygwin does emulate a Unix environment, complete with many Unix commands, those who are tunneling from a Unix-like environment (say, from a Linux machine), can refer to the discussion on Cygwin.</p>
+
+ <div class="courtesylinks">
+ <p><a href="#toc">Top</a> | <a href="/nonav/servlets/HelpTOC">Help index</a></p>
+ </div>
+ </div>
+ </body>
+</html>
+
+
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddSSHGuideterminating.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddSSHGuideterminating.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddSSHGuideterminating.html Sat Apr 8 23:00:09 2017
@@ -0,0 +1,74 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<title>Terminating the tunnel</title>
+
+
+<!--#include virtual="/google-analytics.js" -->
+<!--#include virtual="/scripts/entourage.js" -->
+</head>
+<body>
+<!--#include virtual="/pl/brand.html" -->
+ <div id="topbara">
+ <!--#include virtual="/pl/topnav.html" -->
+ <div id="breadcrumbsa"><a href="/">home</a> » <a href="/pl/">pl</a> » <a href="/pl/Archive/">Archive</a> » <a href="/pl/Archive/trans/">trans</a> » <a href="/pl/Archive/trans/docs/">docs</a> » <a href="/pl/Archive/trans/docs/orig/">orig</a></div>
+ </div>
+ <div id="clear"></div>
+
+
+ <div id="content">
+
+
+
+<span class="PlainText">
+
+
+<p><a name="ddSSHGuideTerminating"</a><span class="Header">Terminating the tunnel</span></p>
+
+
+<span class="PlainText"><b>SSH Guide: Index</b>
+
+<ul>
+ <dl>
+<dt><a href="ddSSHGuide.html">About this guide</a>
+
+<dd><a href="ddSSHGuide.html#aboutssh">About SSH</a></li>
+
+<dd><a href="ddSSHGuide.html#furtherdocumentation">Further documentation</a></li>
+
+<dt><a href="ddSSHGuideConcepts.html">Concepts</a>
+
+<dt><a href="ddSSHGuideChoosing.html">Choosing the desktop terminal</a>
+
+<dt><a href="ddSSHGuideUsingterminals.html">Using the desktop terminal</a>
+
+ <dd><a href="ddSSHGuideTerminals.html#macs">Macintosh</a></dd>
+
+ <dd><a href="ddSSHGuideTerminals.html#windows">Windows</a></dd>
+
+<dt><a href="ddSSHGuideCygwin.html">Tunneling using Cygwin: The Desktop Unix Emulator</a>
+
+<dt><b>You are here: Terminating the tunnel</b>
+
+ </dl>
+</ul>
+<a href="/servlets/HelpTOC">Back to main Help index</a>
+
+<p>
+<hr noshade size=1>
+<span class="InputHeader">Terminating the tunnel</span>
+
+<p>The easiest way to terminate the tunnel is to <span class="TypewriterPlain">Ctrl-C (^C)</span> it out of existence. In both the Mac OS 9.x and Windows environment, you can also close the client window, thereby shutting the tunnel down. Of course, in Mac OS X, the terminal window is closed using control-C.</p>
+
+
+<hr noshade size=1>
+<a href="/servlets/HelpTOC">Back to main Help index</a>
+</span>
+
+ </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddSSHGuideterminating.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddSSHGuideterminating.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddSSHGuideterminating.html.en Sat Apr 8 23:00:09 2017
@@ -0,0 +1,68 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-strict.dtd">
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+<style type="text/css">
+/* <![CDATA[ */ @import "/branding/css/tigris.css"; /* ]]> */
+</style>
+ <script src="/branding/scripts/sc.js" type="text/javascript"></script>
+ <link rel="stylesheet" type="text/css" href="/branding/css/print.css" media="print" />
+
+ <title>Terminating the tunnel</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+ <div class="docs" id="ddsshguideterminating">
+ <h2><a id="ddSSHGuideTerminating" name="ddSSHGuideTerminating">Terminating the tunnel</a></h2>
+
+ <div id="toc">
+ <ul>
+ <li><strong><a href="/nonav/servlets/HelpTOC">Help index</a></strong></li>
+ </ul>
+
+ <ul>
+ <li>
+ <a href="/nonav/docs/ddSSHGuide.html">About this guide</a>
+
+ <ul>
+ <li><a href="/nonav/docs/ddSSHGuide.html#aboutssh">About SSH</a></li>
+
+ <li><a href="/nonav/docs/ddSSHGuide.html#furtherdocumentation">Further documentation</a></li>
+ </ul>
+ </li>
+
+ <li><a href="/nonav/docs/ddSSHGuideConcepts.html">Concepts</a></li>
+
+ <li><a href="/nonav/docs/ddSSHGuideTerminals.html">Choosing the desktop terminal</a></li>
+
+ <li>
+ <a href="/nonav/docs/ddSSHGuideTerminals.html">Using the Desktop Terminal</a>
+
+ <ul>
+ <li><a href="/nonav/docs/ddSSHGuideTerminals.html#macs">Macintosh</a></li>
+
+ <li><a href="/nonav/docs/ddSSHGuideTerminals.html#windows">Windows</a></li>
+
+ <li><a href="/nonav/docs/ddSSHGuideTerminals.html#othersshclients">Other SSH clients</a></li>
+ </ul>
+ </li>
+
+ <li><a href="/nonav/docs/ddSSHGuideCygwin.html">Tunneling using Cygwin: The Desktop Unix Emulator</a></li>
+
+ <li>Terminating the tunnel</li>
+ </ul>
+ </div>
+
+ <h3>Terminating the tunnel</h3>
+
+ <p>The easiest way to terminate the tunnel is to <code>Ctrl-C (^C)</code> it out of existence. In both the Mac OS and Windows environment, you can also close the client window, thereby shutting the tunnel down.</p>
+
+ <div class="courtesylinks">
+ <p><a href="#toc">Top</a> | <a href="/nonav/servlets/HelpTOC">Help index</a></p>
+ </div>
+ </div>
+ </body>
+</html>
+
+
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddSourceBrowse.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddSourceBrowse.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddSourceBrowse.html Sat Apr 8 23:00:09 2017
@@ -0,0 +1,73 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<title>Source Code Browsing with CVSWeb</title>
+
+
+<!--#include virtual="/google-analytics.js" -->
+<!--#include virtual="/scripts/entourage.js" -->
+</head>
+<body>
+<!--#include virtual="/pl/brand.html" -->
+ <div id="topbara">
+ <!--#include virtual="/pl/topnav.html" -->
+ <div id="breadcrumbsa"><a href="/">home</a> » <a href="/pl/">pl</a> » <a href="/pl/Archive/">Archive</a> » <a href="/pl/Archive/trans/">trans</a> » <a href="/pl/Archive/trans/docs/">docs</a> » <a href="/pl/Archive/trans/docs/orig/">orig</a></div>
+ </div>
+ <div id="clear"></div>
+
+
+ <div id="content">
+
+
+
+ <span class="Header" nowrap>Source code browsing online: CVSWeb</span>
+<p>
+ <span class="PlainText" valign="top">
+
+ <p>CVSWeb source code browsing allows the user to browse CVS
+ managed files and their previous versions. Specifically, CVSWeb
+ enables you to:</p>
+
+ <ul>
+ <li>Drill down through directories to get to individual source code files</li>
+ <li>List versions for each file with author name and change log comments</li>
+ <li>View any version of a source file</li>
+ <li>See color-coded the differences between any two versions of a file</li>
+ <li>See files annotated with the author of each section</li>
+ <li>View deleted and removed files (when permitted)
+ </ul>
+
+ <p>Access source code browsing by clicking the <i>Source Code</i>
+ link in the Project menu within any project page. </p>
+
+ <p>CVSWeb is a browser-based interface for CVS
+ repositories. Browse the file hierarchy by selecting directories
+ (designated with slashes after them, e.g. "www/"). When you
+ click on a file, you can view the revision history for that
+ file. Selecting a revision number downloads that revision of the
+ file. Each revision includes a link to display differences
+ between that revision and the previous one. A form at the bottom
+ of the file revision history page allows you to display
+ differences between arbitrary revisions.
+
+<p>
+
+ <p>Look at some <b>examples of browseable CVSWeb source trees</b> on other open source projects:
+ <p>
+ <a href="http://platform.e-speak.net/source/browse/" target="_new">e-speak</a><br>
+ <a href="http://www.netbeans.org/source/browse/" target="_new">netbeans.org</a><br>
+ <a href="http://www.openoffice.org/source/browse/www/www/" target="_new">openoffice.org</a><br>
+ <a href="http://www.mozdev.org/source/browse/" target="_new">mozilla</a><br>
+ or<br>
+ <a href="http://sourceware.cygnus.com/cgi-bin/cvsweb.cgi/" target="_new">Cygnus Sourceware</a>
+ <p>
+
+</span>
+
+ </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddSourceBrowse.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddSourceBrowse.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddSourceBrowse.html.en Sat Apr 8 23:00:09 2017
@@ -0,0 +1,45 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-strict.dtd">
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+<style type="text/css">
+/* <![CDATA[ */ @import "/branding/css/tigris.css"; /* ]]> */
+</style>
+ <script src="/branding/scripts/sc.js" type="text/javascript"></script>
+ <link rel="stylesheet" type="text/css" href="/branding/css/print.css" media="print" />
+
+ <title>Source code browsing</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+ <div class="docs" id="ddsourcebrowse">
+ <h2>Source code browsing online: ViewCVS</h2>
+
+ <p>ViewCVS source code browsing allows the user to browse CVS managed files and their previous versions. Specifically,ViewCVS enables you to:</p>
+
+ <ul>
+ <li>Drill down through directories to get to individual source code files</li>
+
+ <li>List versions for each file with author name and change log comments</li>
+
+ <li>View any version of a source file</li>
+
+ <li>See color-coded the differences between any two versions of a file</li>
+
+ <li>See files annotated with the author of each section</li>
+
+ <li>View deleted and removed files (when permitted)</li>
+ </ul>
+
+ <p>Access source code browsing by clicking the <i>Source Code</i> link in the Project menu within any project page.</p>
+
+ <p>ViewCVS is a browser-based interface for CVS repositories. Browse the file hierarchy by selecting directories (designated with slashes after them, e.g. "www/"). When you click on a file, you can view the revision history for that file. Selecting a revision number downloads that revision of the file. Each revision includes a link to display differences between that revision and the previous one. A form at the bottom of the file revision history page allows you to display differences between arbitrary revisions.</p>
+ <div class="courtesylinks">
+ <p><a href="#toc">Top</a> | <a href="/nonav/servlets/HelpTOC">Help index</a></p>
+ </div>
+ </div>
+ </body>
+</html>
+
+
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddUsingCVS_command-line.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddUsingCVS_command-line.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddUsingCVS_command-line.html Sat Apr 8 23:00:09 2017
@@ -0,0 +1,143 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+<TITLE>Using command-line CVS</TITLE>
+
+<!--#include virtual="/google-analytics.js" -->
+<!--#include virtual="/scripts/entourage.js" -->
+</head>
+<body>
+<!--#include virtual="/pl/brand.html" -->
+ <div id="topbara">
+ <!--#include virtual="/pl/topnav.html" -->
+ <div id="breadcrumbsa"><a href="/">home</a> » <a href="/pl/">pl</a> » <a href="/pl/Archive/">Archive</a> » <a href="/pl/Archive/trans/">trans</a> » <a href="/pl/Archive/trans/docs/">docs</a> » <a href="/pl/Archive/trans/docs/orig/">orig</a></div>
+ </div>
+ <div id="clear"></div>
+
+
+ <div id="content">
+
+
+
+<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
+ <TR>
+ <SPAN CLASS="Header">Using command-line CVS to access project source files</SPAN>
+<P>
+<SPAN CLASS="PlainText"><B>CVS tool documents: Index</B>
+<P>
+<UL>
+<DL>
+<DT><A HREF="ddCVS.html">About source code version control with CVS</A>
+<DT><A HREF="ddCVS_cvsglossary.html">A version control glossary</A>
+<DD><B>You are here: Using CVS to access project source files
+<UL>
+ <LI><A HREF="#cvsintro"><B>Getting started with CVS</B></A>
+ <LI><A HREF="#accesscvs"><B>Accessing a project's CVS repository</B></A>
+ <LI><A HREF="#gettingsource"><B>Getting the source</B></A>
+ <LI><A HREF="#cvslog"><B>Viewing file revision history</B></A>
+</UL></B>
+<DD><A HREF="ddCVS_cvscontributing.html">Contributing source code changes with CVS</A>
+<DD><A HREF="ddCVS_cvsmanaging.html">Managing project files and directories with CVS</A>
+<DT><A HREF="/servlets/HelpTOC">Back to main Help index</A>
+</DL>
+</UL>
+<P>
+<HR NOSHADE SIZE=1>
+<A NAME="cvsintro"></A><SPAN CLASS="InputHeader">Getting started with CVS</SPAN>
+<P>
+If you are participating in a development project on this site, you must use CVS as the versioning control tool for project source files. This the first in a series of three tool documents covering information and commands pertinent to using CVS.
+<P>
+
+<HR NOSHADE SIZE=1>
+<A NAME="accesscvs"></A><SPAN CLASS="InputHeader">Accessing a project's CVS repository</SPAN>
+<P>
+If you do have cvs login access for a project hosted on this site, first you must set the cvsroot to access the project's source code repository. In your shell or terminal client, type:
+<BLOCKQUOTE>
+ <B>:pserver:yourlogin@cvs.projectname.domain.com:/home/main_cvs_dir</B>
+</BLOCKQUOTE>
+<P>substituting your login and project information.
+<P>If you are only working on one project at a time, you only have to set cvsroot the first time you log in to CVS.
+<P>If you are participating in more than one project and need to access CVS repositories located on different servers, you need to set the cvsroot for each login session access the correct project's source repository.
+<P>
+If you do not have a specific cvs login but wish to look at an open source project's source repository, you may still be able to log in to cvs as "anonymous" by typing:
+<BLOCKQUOTE>
+ <B>:pserver:anoncvs@cvs.projectname.domain.com:/home/main_cvs_dir</B>
+</BLOCKQUOTE>
+
+<P>
+<A HREF="http://cvsbook.red-bean.com/cvsbook.html#Accessing_A_Repository" TARGET=_NEW>More about accessing a CVS repository</A>
+<P>
+To log in to CVS, use the following command:<BR>
+<BLOCKQUOTE>
+ <B>cvs login</B><BR>
+</BLOCKQUOTE>
+ Enter your user password when prompted. This should be the same password associated with your user account on this site.
+<P>
+
+<HR NOSHADE SIZE=1>
+
+<SPAN CLASS="InputHeader"><A NAME="gettingsource"></A>Getting source files</SPAN>
+<P>
+ To get a "working copy" of the latest source files, you must check out the source files, a process which copies the files onto your system. First create a directory on your local machine by typing:<BR>
+<BLOCKQUOTE>
+ <B>mkdir my_working_dir</B> (the directory name of your choosing)<BR>
+ <B>cd my_working_dir</B><BR>
+</BLOCKQUOTE>
+<P>
+Then, to check out or copy source file from the repository into your newly created local directory, type:
+<BLOCKQUOTE>
+ <B>cvs checkout project_name</B>
+</BLOCKQUOTE>
+<P>
+This top-level module would contain the entire source code tree (that is, the top level directory and any subdirectories) for that part of the project. There is a fairly common module structure for project CVS repositories initially. As the project grows, the project's source "tree" also grows as subdirectories are added to various modules.
+<P>
+To obtain the source code for a particular module called "module-name" within the project named "project_name", specify:
+<BLOCKQUOTE>
+ <B>cvs checkout module_name/project_name</B>
+</BLOCKQUOTE>
+<P>
+<A HREF="http://cvsbook.red-bean.com/cvsbook.html#Checking_Out_A_Working_Copy" TARGET=_NEW>More about checking out a working copy of project files</A>
+<P>
+
+<HR NOSHADE SIZE=1>
+
+<A NAME="cvslog"></A><SPAN CLASS="InputHeader">Viewing file revision history</SPAN>
+<P>
+Anyone with cvs read permission can view individual file histories to track revision information by typing:
+<BLOCKQUOTE>
+<B>cvs log filename</B>
+</BLOCKQUOTE>
+<P>
+The result is a display of the file's revision information, starting with the most current revision, and includes such information as the log message, status, working revision number, and repository revision number.
+<P>
+<A HREF="http://cvsbook.red-bean.com/cvsbook.html#Revision_Numbers" TARGET="_new">More about file revision numbers</A>
+<P>
+
+<A NAME="cvsdiff"><SPAN CLASS="HelpTextHeader">Comparing file revisions</SPAN></A>
+<P>
+To see the particulars of a file's modifications between two revisions, after obtaining file revision numbering information from the "<B>cvs log</B>" command's output, type:
+<BLOCKQUOTE>
+<B>cvs diff -r revision_# -r revision_#</B>
+</BLOCKQUOTE>
+<P>
+The entire file contents display with lines from both versions where differences occur marked by revision number.
+<P>
+
+<A HREF="http://cvsbook.red-bean.com/cvsbook.html#Finding_Out_What_You__And_Others__Did_--_update_And_diff" TARGET="_new">Finding out what you and others did</A><BR>
+<A HREF="http://cvsbook.red-bean.com/cvsbook.html#diff" TARGET="_new">More about diffs and options</A>
+
+<HR NOSHADE SIZE=1>
+<A HREF="ddCVS_cvscontributing.html">More CVS help: Contributing your changes</A><BR>
+<A HREF="/servlets/HelpTOC">Back to main Help index</A></P></SPAN>
+
+</SPAN>
+</TR>
+</TABLE>
+
+
+ </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddUsingCVS_command-line.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddUsingCVS_command-line.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddUsingCVS_command-line.html.en Sat Apr 8 23:00:09 2017
@@ -0,0 +1,200 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-strict.dtd">
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+<style type="text/css">
+/* <![CDATA[ */ @import "/branding/css/tigris.css"; /* ]]> */
+</style>
+ <script src="/branding/scripts/sc.js" type="text/javascript"></script>
+ <link rel="stylesheet" type="text/css" href="/branding/css/print.css" media="print" />
+
+ <title>Using command-line cvs</title>
+ </head>
+
+ <body class="docs" onLoad="self.focus()">
+ <div class="docs" id="ddusingcvscommandline">
+ <h2>Using command-line CVS to access project source files</h2>
+
+ <div id="toc">
+ <ul>
+ <li><strong><a href="/nonav/servlets/HelpTOC">Help index</a></strong></li>
+ </ul>
+
+ <ul>
+ <li>
+ <a href="/nonav/docs/ddCVS.html">About source code version control with CVS</a>
+
+ <ul>
+ <li><a href="/nonav/docs/ddCVS_cvsglossary.html">A version control glossary</a></li>
+
+ <li>
+ Using command-line CVS to access project source files
+
+ <ul>
+ <li><a href="#cvsintro">Getting started with CVS</a></li>
+ <li><a href="#accesscvs">Accessing a project's CVS repository</a></li>
+ <li><a href="#gettingsource">Getting the source code</a></li>
+ <li><a href="#cvslog">Viewing file revision history</a></li>
+ <li><a href="#cvswatch">Watching files in the CVS repository</a></li>
+ </ul>
+ </li>
+
+ <li><a href="/nonav/docs/ddCVS_cvscontributing.html">Contributing source code changes with CVS</a></li>
+
+ <li><a href="/nonav/docs/ddCVS_cvsmanaging.html">Managing project files and directories with CVS</a></li>
+ </ul>
+ </li>
+ </ul>
+ </div>
+
+ <h3><a id="cvsintro" name="cvsintro">Getting started with CVS</a></h3>
+
+ <p>If you are participating in a development project on this site, you must use CVS as the versioning control tool for project source files. This the first in a series of three tool documents covering information and commands pertinent to using CVS.</p>
+
+ <h3><a id="accesscvs" name="accesscvs">Accessing a project's CVS repository</a></h3>
+
+ <p>If you do have CVS login access for a project hosted on this site, first you must set the CVSroot to access the project's source code repository. In your shell or terminal client, type:</p>
+
+ <p><code>:pserver:yourlogin@CVS.projectname.domain.com:/home/main_CVS_dir</code></p>
+
+ <p>substituting your login and project information.</p>
+
+
+ <p>If you are only working on one project at a time, you only have to set CVSroot
+ the first time you log in to CVS</p>
+
+
+ <p>If you are participating in more than one project and need to access CVS
+ repositories located on different servers, you need to set the CVSroot for
+ each login session access the correct project's source repository.</p>
+
+
+ <p>If you do not have a specific CVS login but wish to look at an open source
+ project's source repository, you may still be able to log in to CVS as "anonymous"
+ by typing:</p>
+
+ <p><code>:pserver:anonCVS@CVS.projectname.domain.com:/home/main_CVS_dir</code></p>
+
+ <ul>
+ <li><a href="http://cvsbook.red-bean.com/cvsbook.html#Accessing_A_Repository">More
+ about accessing a CVS repository</a></li>
+ </ul>
+
+
+ <p>To log in to CVS, use the following command:</p>
+
+
+ <p><code>CVS login</code></p>
+
+ <p>Enter your user password when prompted. This should be the same password associated with your user account on this site.</p>
+
+ <h3><a id="gettingsource" name="gettingsource">Getting source files</a></h3>
+
+ <p>To get a "working copy" of the latest source files, you must check out the source files, a process which copies the files onto your system. First create a directory on your local machine by typing:</p>
+<pre>
+ <code>mkdir my_working_dir (the directory name of your choosing)
+ cd my_working_dir</code>
+
+</pre>
+
+ <p>Then, to check out or copy source file from the repository into your newly created local directory, type:</p>
+
+
+ <p><code>CVS checkout project_name</code></p>
+
+
+ <p>This top-level module would contain the entire source code tree (that is,
+ the top level directory and any subdirectories) for that part of the project.
+ There is a fairly common module structure for project CVS repositories initially.
+ As the project grows, the project's source "tree" also grows as subdirectories
+ are added to various modules.</p>
+
+ <p>To obtain the source code for a particular module called "module-name" within the project named "project_name", specify:</p>
+
+
+ <p><code>CVS checkout module_name/project_name</code></p>
+
+ <p><a href="http://cvsbook.red-bean.com/cvsbook.html#Checking_Out_A_Working_Copy">More about checking out a working copy of project files</a></p>
+
+ <h3><a id="cvslog" name="cvslog">Viewing file revision history</a></h3>
+
+
+ <p>Anyone with CVS read permission can view individual file histories to track
+ revision information by typing:</p>
+
+
+ <p><code>CVS log filename</code></p>
+
+ <p>The result is a display of the file's revision information, starting with the most current revision, and includes such information as the log message, status, working revision number, and repository revision number.</p>
+
+ <ul>
+ <li><a href="http://cvsbook.red-bean.com/cvsbook.html#Revision_Numbers">More about file revision numbers</a></li>
+ </ul>
+
+ <p><a id="cvsdiff" name="cvsdiff"><span class="HelpTextHeader">Comparing file revisions</span></a></p>
+
+
+ <p>To see the particulars of a file's modifications between two revisions, after
+ obtaining file revision numbering information from the "<b>CVS log</b>" command's
+ output, type:</p>
+
+ <p><code>CVS diff -r revision_# -r revision_#</code></p>
+
+ <p>The entire file contents display with lines from both versions where differences occur marked by revision number.</p>
+
+ <ul>
+ <li><a href="http://cvsbook.red-bean.com/cvsbook.html#Finding_Out_What_You__And_Others__Did_--_update_And_diff">Finding out what you and others did</a></li>
+
+ <li><a href="http://cvsbook.red-bean.com/cvsbook.html#diff">More about diffs
+ and options</a></li>
+
+ <li><a href="/nonav/docs/ddCVS_cvscontributing.html">More CVS help: Contributing
+ your changes</a></li>
+ </ul>
+ <h3><a id="cvswatch" name="cvscvswatch">Watching files in the CVS repository</a></h3>
+ <p>You can turn on the "watch" command to tell CVS that you want to
+ receive notifications about actions taken on a file. Too add the current user
+ to the list of people to receive notification of work done on files enter:</p>
+ <p><code>CVS watch add -a [action] -l [files] </code> </p>
+ <p>The -a option specifies what kinds of events CVS should notify the user about.
+ The -a option may appear more than once, or not at all. If omitted, the action
+ defaults to all. Action is one of the following: </p>
+<dl>
+<dd>
+ <dl>
+ <dt>edit </dt>
+ <dd>Another user has applied the CVS edit command (described below) to a file.
+ </dd>
+ <dt>unedit</dt>
+ <dd>Another user has applied the CVS unedit command (described below)
+ or the CVS release command to a file, or has deleted the file and allowed
+ CVS update to recreate it.</dd>
+ <dt>commit</dt>
+ <dd>Another user has committed changes to a file. </dd>
+ <dt>all</dt>
+ <dd>All of the above. </dd>
+ <dt>none </dt>
+ <dd>None of the above. </dd>
+ </dl>
+</dd>
+</dl>
+ <p>The files and -l option are processed as for the CVS watch commands. </p>
+ <p>To remove a notification request established using CVS watch add, the arguments
+ are the same:</p>
+ <p><code>CVS watch remove -a [action] -l [files]</code></p>
+ <p>If the -a option is present, only watches for the specified actions are
+ removed.</p>
+ <p>When the conditions exist for notification, the users will receive an email
+ from the SourceCast server notifying them of the action performed on the files
+ they are watching.</p>
+
+ <div class="courtesylinks">
+
+ <p><a href="#toc">Top</a> | <a href="/nonav/servlets/HelpTOC">Help index</a></p>
+ </div>
+ </div>
+ </body>
+</html>
+
+
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddUsingWinCvs-01.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddUsingWinCvs-01.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddUsingWinCvs-01.html Sat Apr 8 23:00:09 2017
@@ -0,0 +1,137 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<title>Using WinCVS</title>
+
+
+<!--#include virtual="/google-analytics.js" -->
+<!--#include virtual="/scripts/entourage.js" -->
+</head>
+<body>
+<!--#include virtual="/pl/brand.html" -->
+ <div id="topbara">
+ <!--#include virtual="/pl/topnav.html" -->
+ <div id="breadcrumbsa"><a href="/">home</a> » <a href="/pl/">pl</a> » <a href="/pl/Archive/">Archive</a> » <a href="/pl/Archive/trans/">trans</a> » <a href="/pl/Archive/trans/docs/">docs</a> » <a href="/pl/Archive/trans/docs/orig/">orig</a></div>
+ </div>
+ <div id="clear"></div>
+
+
+ <div id="content">
+
+
+
+
+
+<p>
+ <p><span class="Header" nowrap>Checking files in and out of
+ WinCvs</span>
+<p>
+<span class="PlainText">
+ <p> <b>Help for WinCvs: Index</b></p>
+
+
+
+ <dl>
+ <dt><a href="ddUsingWinCvs.html">Setting up WinCvs</a>
+ <dt><b>You are here: Checking source files in and out of WinCvs
+ <ul>
+ <li><a href="#checkingout">Checking out source files</a>
+ <li><a href="#cvsadd">Adding/committing files</a>
+ <li><a href="#cvsupdate">Updating/merging files</a>
+ </ul></b>
+ <dt><a href="ddUsingWinCvs-02.html">Managing files in WinCvs</a></dt>
+ </dl>
+
+<hr noshade size=1>
+ <a name="checkingout"></a><span class="InputHeader">Checking out source
+ files</span> <span class="PlainText">
+ <p>Before you can make changes to source files, you must <i>check out</i>
+ (make a copy on your local hard disk) the project or "module" files you
+ want. A module is a subset of the entire project file repository.</p>
+ <p>Log in to the project's CVS server and provide your password. Then select
+ <strong>Checkout module...</strong> from the <strong>Create</strong> menu
+ to retrieve the latest versions of files. The default selection is <strong><em>all</em></strong>
+ file, or you can select a specific module to check out.</p>
+ <img src="images/wincvs_checkout.gif">
+ <p>You can use the left-hand navigation pane to see the directories and
+ files in that module:</p>
+ <p><img src="images/wincvs_dir.gif"></p>
+ <p> <a href="http://www.cvsgui.org/winhtml/wincvs11.htm#_Toc453646179" target="_new">More
+ about logging in to the project server</a><br>
+ <a href="http://www.cvsgui.org/winhtml/wincvs11.htm#_Toc453646180" target="_new">More
+ about checking out source files</a>
+ <p>
+ <hr noshade size=1>
+ <a name="cvsadd"></a><span class="InputHeader">Adding/committing files</span>
+ <p>WinCvs is not a file editor. You can use the file editor of choice on
+ your local machine to modify project files you have checked out. When
+ you have completed your changes to files on your hard drive, you can <i>commit</i>
+ those changes back into the project's CVS repository.</p>
+ <p>The following example shows the WinCvs window after committing some changes
+ in a directory containing html content files.</p>
+ <p><img src="images/wincvs_afterchange.gif"></p>
+ <p>Whenever you <i>create</i> a new file on your hard disk and you want
+ to add that file to the project, an "unknown file" icon <img src="images/wincvs_unknown_icon.gif">
+ will appear next to your new files.</p>
+ <p>Select the new file and click the "Add Selected" <img src="images/wincvs_addselected.gif">
+ or "Add Selected Binary" <img src="images/wincvs_addbinary.gif"> button
+ in the toolbar to mark the file as under version control. <br>
+ <blockquote>Use "<strong>Add Selected</strong> " for files that are basically
+ text files (e.g., *.txt or *.html).<br>
+ Use "<strong>Add Selected Binary</strong>" for files that have non-text
+ formats (e.g., application data files or graphics).</blockquote>
+ <strong>Note:</strong> Marking the file as "added" <i>does not</i> put it
+ into the project's CVS repository! You must then commit it.
+ <p></p>
+ <p>Files that still need to be committed display a red icon <img src="images/wincvs_modified_icon.gif">
+ next to them. To commit these files:</p>
+ <ol>
+ <li>Select the entire directory in the left-hand pane, or select only
+ those individual files to be committed.
+ <li>Click the commit icon <img src="images/wincvs_commit_icon.gif"> in
+ the tool bar. You are prompted for a log message.
+ <li>Enter a brief description of the changes made to each file.</li>
+ </ol>
+ <p>The results of the committing a file are displayed in the lower right-hand
+ pane. If problems or <i>conflicts</i> are encountered during the merge,
+ WinCvs aborts the commit process. You must then open the file in your
+ file editor, resolve the conflicts, save it again, and then commit. <!--For more about resolving conflicts, see [LINK].-->
+ <p><img src="images/wincvs_commit.gif"></p>
+ <p> <a href="http://www.cvsgui.org/winhtml/wincvs11.htm#_Toc453646186" target="_new">More
+ about adding files</a><br>
+ <a href="http://www.cvsgui.org/winhtml/wincvs11.htm#_Toc453646185" target="_new">More
+ about committing files</a>
+ <p>
+ <hr noshade size=1>
+ <a name="cvsupdate"></a><span class="InputHeader">Updating/merging files</span>
+ <p>You should always update your working copy of the project repository
+ before you commit your changes. This ensures that you are making changes
+ to the most recent versions of files. Updating will not overwrite your
+ modifications if another developer has made changes to the same file(s).
+ Instead, WinCvs attempts to merge the two versions.
+ <p>To update, select <strong>Update files...</strong> on the <strong>CVS
+ Files</strong> menu and select the file(s) or folder(s) you wish to update.
+ <p><img src="images/wincvs_update.gif"></p>
+ <p> <a href="http://www.cvsgui.org/winhtml/wincvs11.htm#_Toc453646181" target="_new">More
+ about updating</a><br>
+ <a href="http://www.cvsgui.org/winhtml/wincvs11.htm#_Toc453646192" target="_new">More
+ about merging</a>
+ </span>
+ <p>For information on file statuses and comparing files, see <a href="ddUsingWinCvs-02.html">Managing
+ files in WinCvs</a>. </p>
+ <span class="PlainText">
+<hr noshade size=1>
+ <a href="/servlets/HelpTOC">Back to main Help index</a>
+ <p></p>
+ </span>
+ <p></p>
+
+</span>
+
+ </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddUsingWinCvs-01.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddUsingWinCvs-01.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddUsingWinCvs-01.html.en Sat Apr 8 23:00:09 2017
@@ -0,0 +1,107 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-strict.dtd">
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+<style type="text/css">
+/* <![CDATA[ */ @import "/branding/css/tigris.css"; /* ]]> */
+</style>
+ <script src="/branding/scripts/sc.js" type="text/javascript"></script>
+ <link rel="stylesheet" type="text/css" href="/branding/css/print.css" media="print" />
+
+ <title>Checking files in and out</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+ <div class="docs" id="ddusingwincvs01">
+ <h2>Checking files in and out of WinCvs</h2>
+
+ <div id="toc">
+ <ul>
+ <li><strong><a href="/nonav/servlets/HelpTOC">Help index</a></strong></li>
+ </ul>
+
+ <ul>
+ <li><a href="/nonav/docs/ddUsingWinCvs.html">Setting up WinCvs</a></li>
+
+ <li>
+ Checking source files in and out of WinCvs
+
+ <ul>
+ <li><a href="#checkingout">Checking out source files</a></li>
+
+ <li><a href="#cvsadd">Adding/committing files</a></li>
+
+ <li><a href="#cvsupdate">Updating/merging files</a></li>
+ </ul>
+ </li>
+
+ <li><a href="/nonav/docs/ddUsingWinCvs-02.html">Managing files in WinCvs</a></li>
+ </ul>
+ </div>
+
+ <h3><a id="checkingout" name="checkingout">Checking out Source Files</a></h3>
+
+ <p>Before you can make changes to source files, you must <i>check out</i> (make a copy on your local hard disk) the project or "module" files you want. A module is a subset of the entire project file repository.</p>
+
+ <p>Log in to the project's CVS server and provide your password. Then select <strong>Checkout module...</strong> from the <strong>Create</strong> menu to retrieve the latest versions of files. You will need to define the module you wish to check out and the directory where you want the checked out files to reside on you local drive.</p>
+
+ <p><a href="http://www.wincvs.org/winhtml/wincvs11.htm#_Toc453646179">More about logging in to the project server</a><br />
+ <a href="http://www.wincvs.org/winhtml/wincvs11.htm#_Toc453646180">More about checking out source files</a></p>
+
+ <h3><a id="cvsupdate" name="cvsupdate">Updating/Merging Files</a></h3>
+
+ <p>You should always update your working copy of the project repository before you commit your changes. This ensures that you are making changes to the most recent versions of files. Updating will not overwrite your modifications if another developer has made changes to the same file(s). Instead, WinCvs attempts to merge the two versions.</p>
+
+ <p>To update, select the file(s) or folder(s) you wish to update and select <strong>Update files...</strong> on the <strong>Modify</strong> menu.</p>
+
+ <ul>
+ <li><a href="http://www.wincvs.org/winhtml/wincvs11.htm#_Toc453646181">More about updating</a></li>
+
+ <li><a href="http://www.wincvs.org/winhtml/wincvs11.htm#_Toc453646192">More about merging</a></li>
+ </ul>
+
+ <p>For information on file statuses and comparing files, see <a href="/nonav/docs/ddUsingWinCvs-02.html">Managing files in WinCvs</a>.</p>
+
+ <h3><a id="cvsadd" name="cvsadd">Adding/Committing Files</a></h3>
+
+ <p>WinCvs is not a file editor. You can use the file editor of choice on your local machine to modify project files you have checked out. When you have completed your changes to files on your hard drive, you can <i>commit</i> those changes back into the project's CVS repository.</p>
+
+ <p>Whenever you <i>create</i> a new file on your hard disk and you want to add that file to the project, an "unknown file" icon <img alt="" src="images/wincvs_unknown_icon.gif" height="15" width="13" /> will appear next to your new files.</p>
+
+ <p>Select the new file and click the "Add Selected" <img alt="" src="images/wincvs_addselected.gif" height="15" width="13" /> or "Add Selected Binary" <img alt="" src="images/wincvs_addbinary.gif" height="15" width="13" /> button in the toolbar to mark the file as under version control.</p>
+
+ <ul>
+ <li>Use "<strong>Add Selected</strong> " for text files (e.g., *.txt or *.html).</li>
+
+ <li>Use "<strong>Add Selected Binary</strong>" for files that have non-text formats (e.g., application data files or graphics).</li>
+ </ul>
+
+ <p><strong>Note:</strong> Adding the file <i>does not</i> put it into the project's CVS repository. You must then commit it.</p>
+
+ <p>Files that still need to be committed display a red icon <img alt="" src="images/wincvs_modified_icon.gif" height="15" width="13" /> next to them. To commit these files:</p>
+
+ <ol>
+ <li>Select the entire directory in the left-hand pane, or select only those individual files to be committed.</li>
+
+ <li>Click the commit icon <img alt="" src="images/wincvs_commit_icon.gif" height="25" width="23" /> in the tool bar. You are prompted for a log message.</li>
+
+ <li>Enter a brief description of the changes made to each file.</li>
+ </ol>
+
+ <p>The results of the committing a file are displayed in the lower pane. If problems or <i>conflicts</i> are encountered during the merge, WinCvs aborts the commit process. You must then open the file in your file editor, resolve the conflicts, save it again, and then commit. <!--For more about resolving conflicts, see [LINK].--></p>
+
+ <ul>
+ <li><a href="http://www.wincvs.org/winhtml/wincvs11.htm#_Toc453646186">More about adding files</a></li>
+
+ <li><a href="http://www.wincvs.org/winhtml/wincvs11.htm#_Toc453646185">More about committing files</a></li>
+ </ul>
+
+ <div class="courtesylinks">
+ <p><a href="#toc">Top</a> | <a href="/nonav/servlets/HelpTOC">Help index</a></p>
+ </div>
+ </div>
+ </body>
+</html>
+
+
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddUsingWinCvs-02.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddUsingWinCvs-02.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddUsingWinCvs-02.html Sat Apr 8 23:00:09 2017
@@ -0,0 +1,114 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<title>Using WinCVS</title>
+
+
+<!--#include virtual="/google-analytics.js" -->
+<!--#include virtual="/scripts/entourage.js" -->
+</head>
+<body>
+<!--#include virtual="/pl/brand.html" -->
+ <div id="topbara">
+ <!--#include virtual="/pl/topnav.html" -->
+ <div id="breadcrumbsa"><a href="/">home</a> » <a href="/pl/">pl</a> » <a href="/pl/Archive/">Archive</a> » <a href="/pl/Archive/trans/">trans</a> » <a href="/pl/Archive/trans/docs/">docs</a> » <a href="/pl/Archive/trans/docs/orig/">orig</a></div>
+ </div>
+ <div id="clear"></div>
+
+
+ <div id="content">
+
+
+
+
+<p>
+ <p><span class="Header" nowrap>Managing files in WinCvs</span>
+
+<span class="PlainText">
+ <p><b>Help for WinCvs: Index</b>
+<p>
+
+
+ <dl>
+ <dt><a href="ddUsingWinCvs.html">Setting up WinCvs</a>
+ <dt><a href="ddUsingWinCvs-01.html">Checking source files in and out of
+ WinCvs</a>
+ <dt><b>You are here: Managing files in WinCvs
+ <ul>
+ <li><a href="#cvstatus">Finding out file status</a>
+ <li><a href="#diff">Comparing different versions
+ of files</a> </li>
+ </ul></b>
+ </dl>
+<hr noshade size=1>
+ <a name="cvstatus"></a><span class="InputHeader">Finding out file status</span>
+ <p>If you need to find the status of a file relative to the version in the CVS repository, select <strong>Status files</strong> in the <strong>CVS files</strong> menu and select the file. The file's status, working revision number, and repository revision number are displayed in the bottom right-hand pane.
+
+<p>CVS status definitions:
+<p>
+<dl>
+ <dt><i>Locally Added</i></dt>
+ <dd>You have added the file with `add', and not yet committed your
+ changes.</dd>
+
+ <dt><i>Locally Removed</i></dt>
+ <dd>You have removed the file with `remove', and not yet committed
+ your changes.</dd>
+
+ <dt><i>Needs Checkout</i></dt>
+ <dd>Someone else has committed a newer revision to the repository.
+ The name is slightly misleading; you will ordinarily use `update'
+ rather than `checkout' to get that newer revision.</dd>
+
+ <dt><i>Needs Patch</i></dt>
+
+ <dd>Like Needs Checkout, but the CVS server will send a patch rather
+ than the entire file. Sending a patch or sending an entire file
+ accomplishes the same thing.</dd>
+
+ <dt><i>Needs Merge</i></dt>
+ <dd>Someone else has committed a newer revision to the repository, and
+ you have also made modifications to the file.</dd>
+
+ <dt><i>File had conflicts on merge</i></dt>
+
+ <dd>This is like Locally Modified, except that a previous `update'
+ command gave a conflict and CVS could not resolve the changes made. If you have not already done so, you need to open the file in an editor and <a href="ddCVS_cvscontributing.html#cvsresolving">resolve the conflict</a>.</dd>
+
+ <dt><i>Unknown</i></dt>
+ <dd>CVS doesn't know anything about this file. For example, you have
+ created a new file and have not run `cvs add'.</dd>
+ </dl>
+
+<p><img src="images/wincvs_status.gif"></p>
+<p>
+
+<p>
+
+<hr noshade size=1>
+ <a name="diff"></a><span class="InputHeader">Comparing different versions
+ of files</span>
+ <p>There may be circumstances when you want to compare the repository version to your file <i>before</i> you commit your changes. Sometimes you may have made some particularly complex modifications to a file that you know someone else has also worked on. Selecting "Diff files..." in the "Cvs files" menu allows you to compare your file against the file in the cvs repository, or against earlier versions.
+
+<p><img src="images/wincvs_diff.gif"></p>
+<p>
+<a href="http://www.cvsgui.org/winhtml/wincvs11.htm#_Toc453646183" target="_new">More about comparing files with diff</a>
+<p>
+
+<p>
+
+<hr noshade size=1>
+<a href="/servlets/HelpTOC">Back to main Help index</a>
+ <p></p>
+
+<p></p>
+
+</span>
+
+ </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddUsingWinCvs-02.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddUsingWinCvs-02.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddUsingWinCvs-02.html.en Sat Apr 8 23:00:09 2017
@@ -0,0 +1,74 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-strict.dtd">
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+<style type="text/css">
+/* <![CDATA[ */ @import "/branding/css/tigris.css"; /* ]]> */
+</style>
+ <script src="/branding/scripts/sc.js" type="text/javascript"></script>
+ <link rel="stylesheet" type="text/css" href="/branding/css/print.css" media="print" />
+
+ <title>Managing files in WinCVS</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+ <div class="docs" id="ddusingwincvs02">
+ <h2>Managing files in WinCvs</h2>
+
+ <div id="toc">
+ <ul>
+ <li><strong><a href="/nonav/servlets/HelpTOC">Help index</a></strong></li>
+ </ul>
+
+ <ul>
+ <li><a href="/nonav/docs/ddUsingWinCvs.html">Setting up WinCvs</a></li>
+
+ <li><a href="/nonav/docs/ddUsingWinCvs-01.html">Checking source files in and out of WinCvs</a></li>
+
+ <li>
+ Managing files in WinCvs
+
+ <ul>
+ <li><a href="#cvstatus">Finding out file status</a></li>
+
+ <li><a href="#diff">Comparing different versions of files</a></li>
+ </ul>
+ </li>
+ </ul>
+ </div>
+
+ <h3><a id="cvstatus" name="cvstatus">Finding out File Status</a></h3>
+
+ <p>If you need to find the status of a file relative to the version in the CVS repository, select the file and select <strong>Status selection</strong> in the <strong>Query</strong> menu. The file's status, working revision number, and repository revision number are displayed in the bottom pane.</p>
+
+ <h4>CVS Status Definitions</h4>
+
+ <dl>
+ <dt>Locally modified</dt>
+
+ <dd>Your working file contains changes made after the latest version in the repository.</dd>
+
+ <dt>Unknown</dt>
+
+ <dd>Your file is not part of the CVS repository. The file needs to be added, then committed.</dd>
+
+ <dt>Up-to-date</dt>
+
+ <dd>Your working file is current with the latest version in the repository. <!-- merge conflict message? --></dd>
+ </dl>
+
+ <h3><a id="diff" name="diff">Comparing Different Versions of Files</a></h3>
+
+ <p>There may be circumstances when you want to compare the repository version to your file <i>before</i> you commit your changes. Sometimes you may have made some particularly complex modifications to a file that you know someone else has also worked on. Selecting <strong>Diff selection</strong> in the <strong>Query</strong> menu allows you to compare your file against the file in the cvs repository, or against earlier versions.</p>
+
+ <p><a href="http://www.wincvs.org/winhtml/wincvs11.htm#_Toc453646183">More about comparing files with diff</a></p>
+
+ <div class="courtesylinks">
+ <p><a href="#toc">Top</a> | <a href="/nonav/servlets/HelpTOC">Help index</a></p>
+ </div>
+ </div>
+ </body>
+</html>
+
+
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddUsingWinCvs.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddUsingWinCvs.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddUsingWinCvs.html Sat Apr 8 23:00:09 2017
@@ -0,0 +1,117 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<title>Using WinCVS</title>
+
+
+<!--#include virtual="/google-analytics.js" -->
+<!--#include virtual="/scripts/entourage.js" -->
+</head>
+<body>
+<!--#include virtual="/pl/brand.html" -->
+ <div id="topbara">
+ <!--#include virtual="/pl/topnav.html" -->
+ <div id="breadcrumbsa"><a href="/">home</a> » <a href="/pl/">pl</a> » <a href="/pl/Archive/">Archive</a> » <a href="/pl/Archive/trans/">trans</a> » <a href="/pl/Archive/trans/docs/">docs</a> » <a href="/pl/Archive/trans/docs/orig/">orig</a></div>
+ </div>
+ <div id="clear"></div>
+
+
+ <div id="content">
+
+
+
+
+ <p>
+ <span class="Header" nowrap>Using WinCvs to work with project source files</span> </p>
+<span class="PlainText">
+ <p>If you are using MS Windows, you can use the graphical client called
+ WinCvs to access a project's version controlled source code files. WinCvs
+ looks and behaves similar to Windows Explorer. You can <a
+ href="http://cvsgui.org/download.html" target=_new>download WinCvs</a> on
+ line and install it on your machine.</p>
+
+
+
+<p> <b>Help for WinCvs: Index</b>
+<ul>
+ <dl>
+ <dt><b>You are here: Setting up WinCvs
+ <ul>
+ <li><a href="#gettingstarted">Getting Started</a></li>
+ <li><a href="#settingcvsroot">Setting up cvsroot</a></li>
+ </ul></b>
+ <dt><a href="ddUsingWinCvs-01.html">Checking source files in and out of WinCvs</a>
+ <dt><a href="ddUsingWinCvs-02.html">Managing files in WinCvs</a> </dt></dl></ul>
+<p>
+
+<hr noshade size=1>
+<a name="gettingstarted"></a><span class="InputHeader">Getting started</span>
+
+<p>When you launch WinCvs, you see a screen that looks like this:</p>
+
+<p><img src="images/wincvs_launch.gif"></p>
+
+<p>Before going further, make a new directory on your
+hard disk where you will store your working copy of the project's source
+files. A good name for this directory is the one-word name of the project
+files you need. If you are working on more than one project, you may wish
+to make a general "<em>projects cvs</em> " folder, and then create subfolders for each project by name. </p>
+
+<p>Select the "<em>project</em>" directory in the
+WinCvs program's left-hand pane. (If you do not see your newly created
+projects directory right away, don't worry! You may need to collapse and
+expand the tree to force it to refresh.) If your project directory is on a
+different drive not displayed in the left-hand WinCvs pane, you will need
+to use the <strong>Change browse location... </strong>command under the
+<strong>View </strong>menu. Be sure to double click on the drive or
+directory you want before clicking <strong>OK</strong>.</p>
+
+<p><img src="images/wincvs_browse.gif"></p>
+<a href="http://www.cvsgui.org/winhtml/wincvs11.htm#_Toc453646172" target="_new">More about setting a work area</a>
+
+<hr noshade size=1>
+<a name="settingcvsroot"></a><span class="InputHeader">Setting up cvsroot</span>
+
+<p> First you must define the location of the WinCvs main repository, the CVSROOT. If you are only working on one project at a time, you only need to set up the cvsroot setup once, i.e. the first time you use WinCvs to access the project's source repository through this site.
+
+<p><ol><li>From the <strong>Admin</strong> menu and select
+<strong>Preferences</strong>
+<p><img src="images/wincvs_prefs.gif"><p></p>
+<li>Replace "username" with your username on the
+ <strong>General</strong> tab.
+
+<li>Click on <strong>Authentication</strong> then
+change the drop down menu to <em>"passwd file on the cvs
+server"</em>.
+
+<li>Click on the <strong>Global</strong> tab.
+
+<p><img src="images/wincvs_global_pref.gif"><p></p>
+<li>Uncheck the "<strong>Checkout read-only</strong>" checkbox.
+
+<li>Click on the <strong>Proxy</strong> tab.
+
+<p><img src="images/wincvs_global_proxy.gif"><p></p>
+<li>Check the "<strong>Connect using a proxy
+server</strong>" checkbox.
+<li>Enter the host name or IP of proxy. For example:
+www.projectname.domain
+<li>Enter port number for the proxy. For example:
+1080</li>
+</ol>
+<p> <a href="http://www.cvsgui.org/winhtml/wincvs11.htm#_Toc453646173" target="_new">More about configuring WinCvs</a></p>
+<p>Now you are ready to begin <a href="ddUsingWinCvs-01.html">Checking source files in and out of WinCvs</a></p>
+
+<p>
+
+<hr noshade size=1>
+<a href="/servlets/HelpTOC">Back to main Help index</a>
+</span>
+
+ </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddUsingWinCvs.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddUsingWinCvs.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/ddUsingWinCvs.html.en Sat Apr 8 23:00:09 2017
@@ -0,0 +1,88 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-strict.dtd">
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+<style type="text/css">
+/* <![CDATA[ */ @import "/branding/css/tigris.css"; /* ]]> */
+</style>
+ <script src="/branding/scripts/sc.js" type="text/javascript"></script>
+ <link rel="stylesheet" type="text/css" href="/branding/css/print.css" media="print" />
+
+ <title>Using WinCvs to Work with Project Source Files</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+ <div class="docs" id="ddusingwincvs">
+ <h2>Using WinCvs to Work with Project Source Files</h2>
+
+ <p>If you are using MS Windows, you can use the graphical client called WinCvs to access a project's version controlled source code files. WinCvs looks and behaves similar to Windows Explorer. You can <a href="http://www.collab.net/developers/tools/">download WinCvs</a> on line and install it on your machine.</p>
+
+ <div id="toc">
+ <ul>
+ <li><strong><a href="/nonav/servlets/HelpTOC">Help index</a></strong></li>
+ </ul>
+
+ <ul>
+ <li>
+ Setting up WinCvs
+
+ <ul>
+ <li><a href="#gettingstarted">Getting Started</a></li>
+
+ <li><a href="#settingcvsroot">Setting up cvsroot</a></li>
+ </ul>
+ </li>
+
+ <li><a href="/nonav/docs/ddUsingWinCvs-01.html">Checking source files in and out of WinCvs</a></li>
+
+ <li><a href="/nonav/docs/ddUsingWinCvs-02.html">Managing files in WinCvs</a></li>
+ </ul>
+ </div>
+
+ <h3><a id="gettingstarted" name="gettingstarted">Getting Started</a></h3>
+
+ <p>After downloading and installing WinCvs, make a new directory on your hard disk where you will store your working copy of the project's source files. A good name for this directory is the one-word name of the project files you need. If you are working on more than one project, you may wish to make a general "<em>projects cvs</em> " folder, and then create subfolders for each project by name.</p>
+
+ <p>Select the "<em>project</em>" directory in the WinCvs program's left-hand pane. (If you do not see your newly created projects directory right away, you may need to refresh your view.) If your project directory is on a different drive not displayed in the left-hand WinCvs pane, you will need to use the <strong>Browse Location>Change</strong> command under the <strong>View</strong> menu. Be sure to double click on the drive or directory you want before clicking <strong>OK</strong>.</p>
+
+ <p><a href="http://www.wincvs.org/winhtml/wincvs11.htm#_Toc453646172">More about setting a work area</a></p>
+
+ <h3><a id="settingcvsroot" name="settingcvsroot">Setting up CVSroot</a></h3>
+
+ <p>First you must define the location of the WinCvs main repository, the CVSROOT. If you are only working on one project at a time, you only need to set up the cvsroot setup once, i.e. the first time you use WinCvs to access the project's source repository through this site.</p>
+
+ <ol>
+ <li>From the <strong>Admin</strong> menu and select <strong>Preferences</strong></li>
+
+ <li>Enter the CVS root in the in the CVS Root field on the <strong>General</strong> tab. The CVS root should appear as: <i>[:pserver:username@projectname.domain.net:/cvs]</i></li>
+
+ <li>Click on <strong>Authentication</strong> then change the drop down menu to <em>"passwd file on the cvs server"</em>.</li>
+
+ <li>Click on the <strong>Global</strong> tab.</li>
+
+ <li>Uncheck the "<strong>Checkout read-only</strong>" checkbox.</li>
+
+ <li>If you are using a Proxy server, you will need to define it on the <strong>Proxy</strong> tab. If you are unsure if you need to use a Proxy server, please contact the site adminitstrator. To define your settings:
+
+ <ol>
+ <li>Check the "<strong>Connect using a proxy server</strong>" checkbox.</li>
+
+ <li>Enter the host name or IP of proxy. For example: [<i>www.projectname.domain</i>]</li>
+
+ <li>Enter port number for the proxy. For example: [<i>1080</i>]</li>
+ </ol>
+ </ol>
+
+ <p><a href="http://www.wincvs.org/winhtml/wincvs11.htm#_Toc453646173">More about configuring WinCvs</a></p>
+
+ <p>Now you are ready to begin <a href="/nonav/docs/ddUsingWinCvs-01.html">Checking source files in and out of WinCvs</a></p>
+
+ <div class="courtesylinks">
+ <p><a href="#toc">Top</a> | <a href="/nonav/servlets/HelpTOC">Help index</a></p>
+ </div>
+ </div>
+ </body>
+</html>
+
+
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/hostedtools.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/hostedtools.html (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/hostedtools.html Sat Apr 8 23:00:09 2017
@@ -0,0 +1,89 @@
+<!--#include virtual="/doctype.html" -->
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+<TITLE>Overview of Hosted Tools</TITLE>
+
+
+<!--#include virtual="/google-analytics.js" -->
+<!--#include virtual="/scripts/entourage.js" -->
+</head>
+<body>
+<!--#include virtual="/pl/brand.html" -->
+ <div id="topbara">
+ <!--#include virtual="/pl/topnav.html" -->
+ <div id="breadcrumbsa"><a href="/">home</a> » <a href="/pl/">pl</a> » <a href="/pl/Archive/">Archive</a> » <a href="/pl/Archive/trans/">trans</a> » <a href="/pl/Archive/trans/docs/">docs</a> » <a href="/pl/Archive/trans/docs/orig/">orig</a></div>
+ </div>
+ <div id="clear"></div>
+
+
+ <div id="content">
+
+
+
+<TABLE BORDER="0 CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
+ <TR>
+ <TD class="Header" nowrap>Overview of Hosted Tools</TD>
+ </TR>
+</TABLE>
+
+<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
+ <TR>
+ <TD class="PlainText">
+
+ <P>This site features the following hosted tools for project
+ members. Each of the following links leads to further
+ documentation about using these tools.
+
+ <P>
+ <DT><A HREF="ddSourceBrowse.html">CVSWeb source code browsing</A>
+
+ <DD><B>CVSWeb</B> source code browsing gives project contributors
+ a graphical, browser-based tool to view project files, version
+ histories, and directory structures.</DD>
+
+ <P>
+ <DT><A HREF="ddCVS.html">CVS source code version control</A>
+
+ <DD>The <B>Concurrent Versions System (CVS)</B> is a widely used
+ version control tool for tracking all modifications to project
+ source code files. Developers can work on the same files and
+ coordinate their contributions through a common repository.</DD>
+
+ <P>
+ <DT><A HREF="ProjectIssues.html#aboutIZ">IssueZilla issue tracking</A>
+
+ <DD><B>IssueZilla</B> is a customizable open-source tool for
+ reporting, tracking, and managing all project tasks, defects,
+ features, enhancements, and patches.</DD>
+ <P>
+
+ <DT><A HREF="ProjectMail.html">Mailing list management and archiving</A>
+
+ <DD>Two open-source mail tools -- <B>anzu</B> and <B>eyebrowse</B> --
+ provide powerful, scalable functionality to administer, moderate,
+ customize, and archive project mailing lists.</DD>
+
+ <P>
+ <DT><A HREF="ddSSHGuide.html">Tunneling with SSH</A>
+
+ <DD><B>SSH</B> provides the security that is required by
+ software development projects. SSH can be used to create a
+ transparent "port tunnel" to the CVS (concurrent versions
+ system) server, unobtrusively insuring the security of the
+ data exchanged.</DD>
+<p>
+<a href="/servlets/HelpTOC">Back to main Help index</a>
+
+
+ </UL>
+ </TD>
+ </TR>
+</TABLE>
+
+ </div>
+<!--#include virtual="/footer.html" -->
+</body>
+</html>
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/hostedtools.html.en
==============================================================================
--- websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/hostedtools.html.en (added)
+++ websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/hostedtools.html.en Sat Apr 8 23:00:09 2017
@@ -0,0 +1,76 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-strict.dtd">
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+<style type="text/css">
+/* <![CDATA[ */ @import "/branding/css/tigris.css"; /* ]]> */
+</style>
+ <script src="/branding/scripts/sc.js" type="text/javascript"></script>
+ <link rel="stylesheet" type="text/css" href="/branding/css/print.css" media="print" />
+
+ <title>Overview of hosted tools</title>
+ </head>
+
+ <body class="docs" onload="self.focus()">
+ <div class="docs" id="hostedtools">
+ <h2>Overview of Hosted Tools</h2>
+
+ <div id="toc">
+ <ul>
+ <li><strong><a href="/nonav/servlets/HelpTOC">Help index</a></strong></li>
+ </ul>
+
+ <ul>
+ <li><a href="/nonav/docs/Learning.html">Learning about projects</a></li>
+
+ <li><a href="/nonav/docs/ProjectMemberResources.html">Project resources for members</a></li>
+
+ <li>Hosted tools</li>
+
+ <li><a href="/nonav/docs/ProjectAdd.html">Creating a new project</a></li>
+ </ul>
+ </div>
+
+ <p>This site features the following hosted tools for project members. Each of the following links leads to further documentation about using these tools.</p>
+
+ <dl>
+ <dt><a href="/nonav/docs/ddSourceBrowse.html">ViewCVS source code browsing</a></dt>
+
+ <dd>
+ <p><b>ViewCVS</b> source code browsing gives project contributors a graphical, browser-based tool to view project files, version histories, and directory structures.</p>
+ </dd>
+
+ <dt><a href="/nonav/docs/ddCVS.html">CVS source code version control</a></dt>
+
+ <dd>
+ <p>The <b>Concurrent Versions System (CVS)</b> is a widely used version control tool for tracking all modifications to project source code files. Developers can work on the same files and coordinate their contributions through a common repository.</p>
+ </dd>
+
+ <dt><a href="/nonav/docs/ProjectIssues.html#aboutIZ">IssueZilla issue tracking</a></dt>
+
+ <dd>
+ <p><b>IssueZilla</b> is a customizable open-source tool for reporting, tracking, and managing all project tasks, defects, features, enhancements, and patches.</p>
+ </dd>
+
+ <dt><a href="/nonav/docs/ProjectMail.html">Mailing list management and archiving</a></dt>
+
+ <dd>
+ <p>Two open-source mail tools -- <b>anzu</b> and <b>eyebrowse</b> -- provide powerful, scalable functionality to administer, moderate, customize, and archive project mailing lists.</p>
+ </dd>
+
+ <dt><a href="/nonav/docs/ddSSHGuide.html">Tunneling with SSH</a></dt>
+
+ <dd>
+ <p><b>SSH</b> provides the security that is required by software development projects. SSH can be used to create a transparent "port tunnel" to the CVS (concurrent versions system) server, unobtrusively insuring the security of the data exchanged.</p>
+ </dd>
+ </dl>
+
+ <div class="courtesylinks">
+ <p><a href="#toc">Top</a> | <a href="/nonav/servlets/HelpTOC">Help index</a></p>
+ </div>
+ </div>
+ </body>
+</html>
+
+
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_addbinary.gif
==============================================================================
Binary file - no diff available.
Propchange: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_addbinary.gif
------------------------------------------------------------------------------
svn:mime-type = image/gif
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_addselected.gif
==============================================================================
Binary file - no diff available.
Propchange: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_addselected.gif
------------------------------------------------------------------------------
svn:mime-type = image/gif
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_afterchange.gif
==============================================================================
Binary file - no diff available.
Propchange: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_afterchange.gif
------------------------------------------------------------------------------
svn:mime-type = image/gif
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_browse.gif
==============================================================================
Binary file - no diff available.
Propchange: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_browse.gif
------------------------------------------------------------------------------
svn:mime-type = image/gif
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_checkout.gif
==============================================================================
Binary file - no diff available.
Propchange: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_checkout.gif
------------------------------------------------------------------------------
svn:mime-type = image/gif
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_commit.gif
==============================================================================
Binary file - no diff available.
Propchange: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_commit.gif
------------------------------------------------------------------------------
svn:mime-type = image/gif
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_commit_icon.gif
==============================================================================
Binary file - no diff available.
Propchange: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_commit_icon.gif
------------------------------------------------------------------------------
svn:mime-type = image/gif
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_diff.gif
==============================================================================
Binary file - no diff available.
Propchange: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_diff.gif
------------------------------------------------------------------------------
svn:mime-type = image/gif
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_dir.gif
==============================================================================
Binary file - no diff available.
Propchange: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_dir.gif
------------------------------------------------------------------------------
svn:mime-type = image/gif
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_global_pref.gif
==============================================================================
Binary file - no diff available.
Propchange: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_global_pref.gif
------------------------------------------------------------------------------
svn:mime-type = image/gif
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_global_proxy.gif
==============================================================================
Binary file - no diff available.
Propchange: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_global_proxy.gif
------------------------------------------------------------------------------
svn:mime-type = image/gif
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_launch.gif
==============================================================================
Binary file - no diff available.
Propchange: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_launch.gif
------------------------------------------------------------------------------
svn:mime-type = image/gif
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_login.gif
==============================================================================
Binary file - no diff available.
Propchange: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_login.gif
------------------------------------------------------------------------------
svn:mime-type = image/gif
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_modified_icon.gif
==============================================================================
Binary file - no diff available.
Propchange: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_modified_icon.gif
------------------------------------------------------------------------------
svn:mime-type = image/gif
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_prefs.gif
==============================================================================
Binary file - no diff available.
Propchange: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_prefs.gif
------------------------------------------------------------------------------
svn:mime-type = image/gif
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_status.gif
==============================================================================
Binary file - no diff available.
Propchange: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_status.gif
------------------------------------------------------------------------------
svn:mime-type = image/gif
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_unknown_icon.gif
==============================================================================
Binary file - no diff available.
Propchange: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_unknown_icon.gif
------------------------------------------------------------------------------
svn:mime-type = image/gif
Added: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_update.gif
==============================================================================
Binary file - no diff available.
Propchange: websites/staging/ooo-site/trunk/content/pl/Archive/trans/docs/orig/images/wincvs_update.gif
------------------------------------------------------------------------------
svn:mime-type = image/gif