You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-commits@db.apache.org by cl...@apache.org on 2005/09/02 21:31:14 UTC
svn commit: r267281 - in /incubator/jdo/site: docs/svn.html xdocs/svn.xml
Author: clr
Date: Fri Sep 2 12:31:12 2005
New Revision: 267281
URL: http://svn.apache.org/viewcvs?rev=267281&view=rev
Log:
Updated svn information; work in progress
Modified:
incubator/jdo/site/docs/svn.html
incubator/jdo/site/xdocs/svn.xml
Modified: incubator/jdo/site/docs/svn.html
URL: http://svn.apache.org/viewcvs/incubator/jdo/site/docs/svn.html?rev=267281&r1=267280&r2=267281&view=diff
==============================================================================
--- incubator/jdo/site/docs/svn.html (original)
+++ incubator/jdo/site/docs/svn.html Fri Sep 2 12:31:12 2005
@@ -119,16 +119,20 @@
</td></tr>
<tr><td>
<blockquote>
- <p>
-The JDO project uses the
-<a href="http://subversion.tigris.org/">Subversion</a> version control
-system. If you're new to Subversion, you can check out the
+ <p>Apache JDO uses <a class="external" rel="nofollow" href="http://subversion.tigris.org">Subversion</a> to manage its source code. Instructions on Subversion use can be found <a class="external" rel="nofollow" href="http://svnbook.red-bean.com">here</a>. To receive notice of commits to the repository subscribe to <a href="mailto:jdo-commits@db.apache.org">jdo-commits@db.apache.org</a> by sending email to <a href="mailto:jdo-commits-subscribe@db.apache.org">jdo-commits-subscribe@db.apache.org</a>. </p>
+ <p>
+If you're new to Subversion, you can check out the
<a href="http://svnbook.red-bean.com/">online book</a> about Subversion.
Note that we are currently using Subversion 1.1.x (there are separate
versions of the book covering 1.0 and 1.1).
</p>
- <table border="0" cellspacing="0" cellpadding="2" width="100%">
- <tr><td bgcolor="#828DA6">
+ </blockquote>
+ </p>
+ </td></tr>
+ <tr><td><br/></td></tr>
+ </table>
+ <table border="0" cellspacing="0" cellpadding="2" width="100%">
+ <tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="Web Access to Subversion"><strong>Web Access to Subversion</strong></a>
</font>
@@ -141,11 +145,12 @@
web interface</a> to Subversion. This is current at all times.
</p>
</blockquote>
+ </p>
</td></tr>
<tr><td><br/></td></tr>
</table>
- <table border="0" cellspacing="0" cellpadding="2" width="100%">
- <tr><td bgcolor="#828DA6">
+ <table border="0" cellspacing="0" cellpadding="2" width="100%">
+ <tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="Normal Subversion Access"><strong>Normal Subversion Access</strong></a>
</font>
@@ -179,11 +184,12 @@
will remember it for you. Note this is the password you configured with
<tt>svnpasswd</tt>, not your shell or other password.</p>
</blockquote>
+ </p>
</td></tr>
<tr><td><br/></td></tr>
</table>
- <table border="0" cellspacing="0" cellpadding="2" width="100%">
- <tr><td bgcolor="#828DA6">
+ <table border="0" cellspacing="0" cellpadding="2" width="100%">
+ <tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="Building JDO from Source"><strong>Building JDO from Source</strong></a>
</font>
@@ -194,9 +200,146 @@
page</a> for details. Note that the JDO project is subdivided into several
smaller projects, and each project is built separately. </p>
</blockquote>
+ </p>
+ </td></tr>
+ <tr><td><br/></td></tr>
+ </table>
+ <table border="0" cellspacing="0" cellpadding="2" width="100%">
+ <tr><td bgcolor="#525D76">
+ <font color="#ffffff" face="arial,helvetica,sanserif">
+ <a name="Current Version"><strong>Current Version</strong></a>
+ </font>
+ </td></tr>
+ <tr><td>
+ <blockquote>
+ <p>The Apache subversion repository contains the latest code. </p>
+ <p><strong>Previous versions</strong> </p>
+ <p>Download the 2005-03-08 version <a href="/jdo-data/attachments/SubversionRepository/attachments/apache-jdo-2005-03-08.zip">here</a>. It implements the remaining JDO TCK 1 query test cases. The subproject structure has been changed by adding directories java, dtd, jdo, etc. under src and test. The tck11 subproject uses some basic test configuration as described in <a href="/jdo/TestRunner">TestRunner</a>. </p>
+ <p>Download the 2005-02-17 version <a href="/jdo-data/attachments/SubversionRepository/attachments/apache-jdo-2005-02-17.zip">here</a>. It fixes a problem with running the ri11/tck11 subprojects under windows. Furthermore it updates some TCK query tests. </p>
+ <p>Download the 2005-02-10 version <a href="/jdo-data/attachments/SubversionRepository/attachments/apache-jdo-2005-02-10.zip">here</a>. It includes logging changes and support for running the jars with J2SE 1.3. </p>
+ <p>Download the 2005-01-21 version <a href="/jdo-data/attachments/SubversionRepository/attachments/apache-jdo-2005-01-21.zip">here</a>. It includes a working copy of the tck11 sub-project. </p>
+ <p>Download the 2005-01-14 version <a href="/jdo-data/attachments/SubversionRepository/attachments/apache-jdo-2005-01-14.zip">here</a>. </p>
+ <p>Download the 2004-12-13 version <a href="/jdo-data/attachments/SubversionRepository/attachments/apache-jdo-2004-12-13.zip">here</a>. </p>
+ </blockquote>
+ </p>
</td></tr>
<tr><td><br/></td></tr>
</table>
+ <table border="0" cellspacing="0" cellpadding="2" width="100%">
+ <tr><td bgcolor="#525D76">
+ <font color="#ffffff" face="arial,helvetica,sanserif">
+ <a name="Everything else"><strong>Everything else</strong></a>
+ </font>
+ </td></tr>
+ <tr><td>
+ <blockquote>
+ <h2 id="head-b4db92eef118cd96f75654326d629108ab1b2ebf">Web Access</h2>
+ <p><a class="external" rel="nofollow" href="http://svn.apache.org/viewcvs/incubator/jdo"><img src="/wiki/modern/img/moin-www.png" alt="[WWW]" height="11" width="11" /> http://svn.apache.org/viewcvs/incubator/jdo</a> </p>
+ <h2 id="head-69f36b261cdd6a451d71afd071e980facb8efd18">Anonymous access</h2>
+ <p>Apache JDO source can be checked out anonymously with this command: </p>
+ <ul>
+<li style="list-style-type:none">
+<pre>
+% svn checkout http://svn.apache.org/repos/asf/incubator/jdo
+</pre>
+</li>
+</ul>
+ <p>Once you have Apacje JDO checked out you can update the source by executing the following command from within the jdo. </p>
+ <ul>
+<li style="list-style-type:none">
+<pre>
+% svn update
+</pre>
+</li>
+</ul>
+ <h2 id="head-33604d44bc68f38236ff0009b6b6e1797ae2439b">Access from behind a firewall</h2>
+ <p>For those users who are stuck behind a corporate firewall which is blocking http access to the Subversion repository, you can try to access it via HTTPS: </p>
+ <ul>
+<li style="list-style-type:none">
+<pre>
+% svn checkout https://svn.apache.org/repos/asf/incubator/jdo
+</pre>
+</li>
+</ul>
+ <h2 id="head-097c9dce4eeef776d9a83883743ceb63828dd02a">Access through a proxy</h2>
+ <p>The Subversion client can go through a proxy, if you configure it to do so. First, edit your "servers" configuration file to indicate which proxy to use. The files location depends on your operating system. On Linux or Unix it is located in the directory "~/.subversion". On Windows it is in "%APPDATA%\Subversion". (Try "echo %APPDATA%", note this is a hidden directory.) </p>
+ <p>There are comments in the file explaining what to do. If you don't have that file, get the latest Subversion client and run any command; this will cause the configuration directory and template files to be created. </p>
+ <p>Example : Edit the 'servers' file and add something like : </p>
+ <ul>
+<li style="list-style-type:none">
+<pre>
+[global]
+http-proxy-host = your.proxy.name
+http-proxy-port = 3128
+</pre>
+</li>
+</ul>
+ <p>Please use the regular http proxy settings in case you want to access the the repository from the Sun network (SWAN). </p>
+ <h2 id="head-9c935033e1dc50f91ed53944598dc136159bab9a">Submitting a Patch</h2>
+ <p>If you make changes to Apache JDO, and would like to contribute the to the project, you should create a patch and send it to the jdo-dev alias <a href="mailto:jdo-dev@db.apache.org"><img src="/wiki/modern/img/moin-email.png" alt="[MAILTO]" height="10" width="14" /> jdo-dev@db.apache.org</a>. To create a patch, simply execute the following command: </p>
+ <ul>
+<li style="list-style-type:none">
+<pre>
+% svn diff > your-changes.patch
+</pre>
+</li>
+</ul>
+ <h2 id="head-253262c428af230484d34abd39cfd93de3b353c2">Developer Access</h2>
+ <p>Everyone can access the Apache JDO Subversion repository via HTTPS, but Apache JDO Committers must checkout the Subversion repository via HTTPS. </p>
+ <ul>
+<li style="list-style-type:none">
+<pre>
+% svn checkout https://svn.apache.org/repos/asf/incubator/jdo
+</pre>
+</li>
+</ul>
+ <p>To commit changes to the repository, you must set your password on the Apache Subversion server. To set your password, use ssh to connect to svn.apache.org, and enter the command <strong>svnpasswd</strong>. This will prompt you to enter a svn password of your choice (pick a safe password). Now, now your are ready to commit changes using your username/password. Execute the following command to commit your changes (svn will prompt you for your password) </p>
+ <ul>
+<li style="list-style-type:none">
+<pre>
+$> svn commit --username your-username
+Authentication realm: <https://svn.apache.org:443> ASF Committers
+Password for 'your-username': your-password
+</pre>
+</li>
+</ul>
+ <p>You can also pass your password on the command line directly, but this is a security problem on multiuser unix computers (the command line arguments are available via the ps command). Here is the command if you are Windows or a single user unix computer: </p>
+ <ul>
+<li style="list-style-type:none">
+<pre>
+$> svn commit --username your-username --password your-password
+</pre>
+</li>
+</ul>
+ <p>Remember to replace 'your-username' and 'your-password' with your actual username and password on svn.apache.org. </p>
+ <h2 id="head-8e58b63eac33a4eaa91c2926015d99401b80ef5b">NetBeans CVS Repository Access</h2>
+ <p>The btree subproject checks out the NetBeans mdr btree implementation. This requires cvs being installed on your system. The official NetBeans cvs host might not work if you are behind a firewall that blocks the cvs port. Please consult the <a class="external" rel="nofollow" href="http://www.netbeans.org/community/sources"><img src="/wiki/modern/img/moin-www.png" alt="[WWW]" height="11" width="11" /> NetBeans sources</a> page for more info. </p>
+ <p>If you do not have a cvs client installed on your system you can download the NetBeans mdr btree sources <a href="/jdo-data/attachments/SubversionRepository/attachments/netbeans-mdr-btree.zip">here</a>. Unzip the file in the btree directory and comment out (or remove) the definition of the preGoal java:prepare-filesystem. </p>
+ <h2 id="head-496a9059e3fcee99aa23246c9c99caa907cc696c">Using subversion on Windows with cygwin</h2>
+ <p>If you use subversion on Windows under cygwin, you may find that the subversion client automatically assigns the executable property to non-executable files. In that case, you would see this at the bottom of an <em>svn diff</em> of the file:
+</p>
+ <pre>
+Property changes on: test/sql/derby/datastoreidentity/schema1.sql
+___________________________________________________________________
+Name: svn:executable
+ + *
+</pre>
+ <p>This section explains the source of the problem and suggests some actions to avoid it. </p>
+ <h3 id="head-25f2f810af0c983529ce4e0cf1c97a1c79407d37">Background</h3>
+ <p>Subversion carries executable information in the built-in property called svn:executable. This property, unlike others, may be present or absent, but it has no value. You can add it or delete it, but but you cannot change its value. </p>
+ <p>In theory, subversion ignores Windows file permissions and by default does not set svn:executable. However, cygwin svn acts like Unix svn and determines the svn:executable property based on file permissions. </p>
+ <p>If you create a file from the cygwin command line, by default it is executable only if the filename ends with .bat, .com or .exe, or if its content starts with #!. [This is what the doc says, but you may see -x for all files.] If you create a file using a Windows tool, by default its Windows permissions are executable by all. Cygwin interprets the Unix-style permissions this way as well. If the file is executable by all, cygwin svn sets the svn:executable property on the file when you invoke <em>svn add</em>. </p>
+ <h3 id="head-30974b27025652b23debaf98550ad8f306b4f514">Removing existing executable properties from the repository</h3>
+ <p>You can use svn propdel to remove the svn:executable property from your working copy.
+</p>
+ <pre>
+ svn propdel -R svn:executable .
+</pre>
+ <p>will recursively remove the svn:executable property from all of the files below the current directory. You can use this and commit the files to clean the repository if necessary. </p>
+ <h3 id="head-83054b7348b09c545266af376baebd316a69fb9a">Preventing subversion from adding unwanted executable properties</h3>
+ <p>Windows/cygwin users who don't want to have to think about using <em>svn propdel</em> or <em>chmod</em> on each added file can use a non-cygwin version of svn. The Subversion 1.2.3 Win32 binaries, downloadable from the link at the bottom of <a rel="nofollow" href="http://subversion.tigris.org/project_packages.html"><img src="/wiki/modern/img/moin-www.png" alt="[WWW]" height="11" width="11" /> http://subversion.tigris.org/project_packages.html</a>, appear to work well. After installation, add the svn.exe location to your Windows PATH variable. You must also remove the subversion component from your cygwin installation because when svn is invoked from a cygwin window, the cygwin version is found even if your cygwin/bin directory is later on the path. </p>
+ <p>Alternatively, Windows users can set file permissions in Windows Explorer. (Right-click on the top-level folder & select Properties. Select the Security tab. Click Advanced. Remove all instances of Read & Execute from the Permission Entries. Click "Reset permissions on all child objects and enable propogations of inheritable permissions". Click Apply. OK. OK.) You will have to do this again when you do a clean checkout to a new directory. </p>
+ <a id="bottom" />
</blockquote>
</p>
</td></tr>
Modified: incubator/jdo/site/xdocs/svn.xml
URL: http://svn.apache.org/viewcvs/incubator/jdo/site/xdocs/svn.xml?rev=267281&r1=267280&r2=267281&view=diff
==============================================================================
--- incubator/jdo/site/xdocs/svn.xml (original)
+++ incubator/jdo/site/xdocs/svn.xml Fri Sep 2 12:31:12 2005
@@ -28,16 +28,17 @@
<section name="Apache JDO Source Code">
+<p>Apache JDO uses <a class="external" rel="nofollow" href="http://subversion.tigris.org">Subversion</a> to manage its source code. Instructions on Subversion use can be found <a class="external" rel="nofollow" href="http://svnbook.red-bean.com">here</a>. To receive notice of commits to the repository subscribe to <a href="mailto:jdo-commits@db.apache.org">jdo-commits@db.apache.org</a> by sending email to <a href="mailto:jdo-commits-subscribe@db.apache.org">jdo-commits-subscribe@db.apache.org</a>. </p>
<p>
-The JDO project uses the
-<a href="http://subversion.tigris.org/">Subversion</a> version control
-system. If you're new to Subversion, you can check out the
+If you're new to Subversion, you can check out the
<a href="http://svnbook.red-bean.com/">online book</a> about Subversion.
Note that we are currently using Subversion 1.1.x (there are separate
versions of the book covering 1.0 and 1.1).
</p>
-<subsection name="Web Access to Subversion">
+</section>
+
+<section name="Web Access to Subversion">
<p>
If you just want to browse the source code, you can use the
@@ -46,9 +47,9 @@
web interface</a> to Subversion. This is current at all times.
</p>
-</subsection>
+</section>
-<subsection name="Normal Subversion Access">
+<section name="Normal Subversion Access">
<p>Anyone can check code out of Subversion. You need to specify a
username and password in order to update the Subversion repository, and only
@@ -83,14 +84,158 @@
will remember it for you. Note this is the password you configured with
<tt>svnpasswd</tt>, not your shell or other password.</p>
-</subsection>
+</section>
-<subsection name="Building JDO from Source">
+<section name="Building JDO from Source">
<p>Refer to the <a href="http://wiki.apache.org/jdo/FrontPage">Wiki
page</a> for details. Note that the JDO project is subdivided into several
smaller projects, and each project is built separately. </p>
-</subsection>
+</section>
+
+<section name="Current Version">
+
+<p>The Apache subversion repository contains the latest code. </p>
+<p><strong>Previous versions</strong> </p>
+<p>Download the 2005-03-08 version <a href="/jdo-data/attachments/SubversionRepository/attachments/apache-jdo-2005-03-08.zip">here</a>. It implements the remaining JDO TCK 1 query test cases. The subproject structure has been changed by adding directories java, dtd, jdo, etc. under src and test. The tck11 subproject uses some basic test configuration as described in <a href="/jdo/TestRunner">TestRunner</a>. </p>
+<p>Download the 2005-02-17 version <a href="/jdo-data/attachments/SubversionRepository/attachments/apache-jdo-2005-02-17.zip">here</a>. It fixes a problem with running the ri11/tck11 subprojects under windows. Furthermore it updates some TCK query tests. </p>
+<p>Download the 2005-02-10 version <a href="/jdo-data/attachments/SubversionRepository/attachments/apache-jdo-2005-02-10.zip">here</a>. It includes logging changes and support for running the jars with J2SE 1.3. </p>
+<p>Download the 2005-01-21 version <a href="/jdo-data/attachments/SubversionRepository/attachments/apache-jdo-2005-01-21.zip">here</a>. It includes a working copy of the tck11 sub-project. </p>
+<p>Download the 2005-01-14 version <a href="/jdo-data/attachments/SubversionRepository/attachments/apache-jdo-2005-01-14.zip">here</a>. </p>
+<p>Download the 2004-12-13 version <a href="/jdo-data/attachments/SubversionRepository/attachments/apache-jdo-2004-12-13.zip">here</a>. </p>
+
+</section>
+
+<section name="Everything else">
+
+<h2 id="head-b4db92eef118cd96f75654326d629108ab1b2ebf">Web Access</h2>
+
+<p><a class="external" rel="nofollow" href="http://svn.apache.org/viewcvs/incubator/jdo"><img src="/wiki/modern/img/moin-www.png" alt="[WWW]" height="11" width="11"/> http://svn.apache.org/viewcvs/incubator/jdo</a> </p>
+
+<h2 id="head-69f36b261cdd6a451d71afd071e980facb8efd18">Anonymous access</h2>
+
+<p>Apache JDO source can be checked out anonymously with this command: </p>
+<ul>
+<li style="list-style-type:none">
+<pre>
+% svn checkout http://svn.apache.org/repos/asf/incubator/jdo
+</pre>
+</li>
+</ul>
+<p>Once you have Apacje JDO checked out you can update the source by executing the following command from within the jdo. </p>
+<ul>
+<li style="list-style-type:none">
+<pre>
+% svn update
+</pre>
+</li>
+</ul>
+
+<h2 id="head-33604d44bc68f38236ff0009b6b6e1797ae2439b">Access from behind a firewall</h2>
+
+<p>For those users who are stuck behind a corporate firewall which is blocking http access to the Subversion repository, you can try to access it via HTTPS: </p>
+<ul>
+<li style="list-style-type:none">
+<pre>
+% svn checkout https://svn.apache.org/repos/asf/incubator/jdo
+</pre>
+</li>
+</ul>
+
+<h2 id="head-097c9dce4eeef776d9a83883743ceb63828dd02a">Access through a proxy</h2>
+
+<p>The Subversion client can go through a proxy, if you configure it to do so. First, edit your "servers" configuration file to indicate which proxy to use. The files location depends on your operating system. On Linux or Unix it is located in the directory "~/.subversion". On Windows it is in "%APPDATA%\Subversion". (Try "echo %APPDATA%", note this is a hidden directory.) </p>
+<p>There are comments in the file explaining what to do. If you don't have that file, get the latest Subversion client and run any command; this will cause the configuration directory and template files to be created. </p>
+<p>Example : Edit the 'servers' file and add something like : </p>
+<ul>
+<li style="list-style-type:none">
+<pre>
+[global]
+http-proxy-host = your.proxy.name
+http-proxy-port = 3128
+</pre>
+</li>
+</ul>
+<p>Please use the regular http proxy settings in case you want to access the the repository from the Sun network (SWAN). </p>
+
+<h2 id="head-9c935033e1dc50f91ed53944598dc136159bab9a">Submitting a Patch</h2>
+
+<p>If you make changes to Apache JDO, and would like to contribute the to the project, you should create a patch and send it to the jdo-dev alias <a href="mailto:jdo-dev@db.apache.org"><img src="/wiki/modern/img/moin-email.png" alt="[MAILTO]" height="10" width="14"/> jdo-dev@db.apache.org</a>. To create a patch, simply execute the following command: </p>
+<ul>
+<li style="list-style-type:none">
+<pre>
+% svn diff > your-changes.patch
+</pre>
+</li>
+</ul>
+
+<h2 id="head-253262c428af230484d34abd39cfd93de3b353c2">Developer Access</h2>
+
+<p>Everyone can access the Apache JDO Subversion repository via HTTPS, but Apache JDO Committers must checkout the Subversion repository via HTTPS. </p>
+<ul>
+<li style="list-style-type:none">
+<pre>
+% svn checkout https://svn.apache.org/repos/asf/incubator/jdo
+</pre>
+</li>
+</ul>
+<p>To commit changes to the repository, you must set your password on the Apache Subversion server. To set your password, use ssh to connect to svn.apache.org, and enter the command <strong>svnpasswd</strong>. This will prompt you to enter a svn password of your choice (pick a safe password). Now, now your are ready to commit changes using your username/password. Execute the following command to commit your changes (svn will prompt you for your password) </p>
+<ul>
+<li style="list-style-type:none">
+<pre>
+$> svn commit --username your-username
+Authentication realm: <https://svn.apache.org:443> ASF Committers
+Password for 'your-username': your-password
+</pre>
+</li>
+</ul>
+<p>You can also pass your password on the command line directly, but this is a security problem on multiuser unix computers (the command line arguments are available via the ps command). Here is the command if you are Windows or a single user unix computer: </p>
+<ul>
+<li style="list-style-type:none">
+<pre>
+$> svn commit --username your-username --password your-password
+</pre>
+</li>
+</ul>
+<p>Remember to replace 'your-username' and 'your-password' with your actual username and password on svn.apache.org. </p>
+
+<h2 id="head-8e58b63eac33a4eaa91c2926015d99401b80ef5b">NetBeans CVS Repository Access</h2>
+
+<p>The btree subproject checks out the NetBeans mdr btree implementation. This requires cvs being installed on your system. The official NetBeans cvs host might not work if you are behind a firewall that blocks the cvs port. Please consult the <a class="external" rel="nofollow" href="http://www.netbeans.org/community/sources"><img src="/wiki/modern/img/moin-www.png" alt="[WWW]" height="11" width="11"/> NetBeans sources</a> page for more info. </p>
+<p>If you do not have a cvs client installed on your system you can download the NetBeans mdr btree sources <a href="/jdo-data/attachments/SubversionRepository/attachments/netbeans-mdr-btree.zip">here</a>. Unzip the file in the btree directory and comment out (or remove) the definition of the preGoal java:prepare-filesystem. </p>
+
+<h2 id="head-496a9059e3fcee99aa23246c9c99caa907cc696c">Using subversion on Windows with cygwin</h2>
+
+<p>If you use subversion on Windows under cygwin, you may find that the subversion client automatically assigns the executable property to non-executable files. In that case, you would see this at the bottom of an <em>svn diff</em> of the file:
+</p>
+<pre>
+Property changes on: test/sql/derby/datastoreidentity/schema1.sql
+___________________________________________________________________
+Name: svn:executable
+ + *
+</pre>
+<p>This section explains the source of the problem and suggests some actions to avoid it. </p>
+
+<h3 id="head-25f2f810af0c983529ce4e0cf1c97a1c79407d37">Background</h3>
+
+<p>Subversion carries executable information in the built-in property called svn:executable. This property, unlike others, may be present or absent, but it has no value. You can add it or delete it, but but you cannot change its value. </p>
+<p>In theory, subversion ignores Windows file permissions and by default does not set svn:executable. However, cygwin svn acts like Unix svn and determines the svn:executable property based on file permissions. </p>
+<p>If you create a file from the cygwin command line, by default it is executable only if the filename ends with .bat, .com or .exe, or if its content starts with #!. [This is what the doc says, but you may see -x for all files.] If you create a file using a Windows tool, by default its Windows permissions are executable by all. Cygwin interprets the Unix-style permissions this way as well. If the file is executable by all, cygwin svn sets the svn:executable property on the file when you invoke <em>svn add</em>. </p>
+
+<h3 id="head-30974b27025652b23debaf98550ad8f306b4f514">Removing existing executable properties from the repository</h3>
+
+<p>You can use svn propdel to remove the svn:executable property from your working copy.
+</p>
+<pre>
+ svn propdel -R svn:executable .
+</pre>
+<p>will recursively remove the svn:executable property from all of the files below the current directory. You can use this and commit the files to clean the repository if necessary. </p>
+
+<h3 id="head-83054b7348b09c545266af376baebd316a69fb9a">Preventing subversion from adding unwanted executable properties</h3>
+
+<p>Windows/cygwin users who don't want to have to think about using <em>svn propdel</em> or <em>chmod</em> on each added file can use a non-cygwin version of svn. The Subversion 1.2.3 Win32 binaries, downloadable from the link at the bottom of <a rel="nofollow" href="http://subversion.tigris.org/project_packages.html"><img src="/wiki/modern/img/moin-www.png" alt="[WWW]" height="11" width="11"/> http://subversion.tigris.org/project_packages.html</a>, appear to work well. After installation, add the svn.exe location to your Windows PATH variable. You must also remove the subversion component from your cygwin installation because when svn is invoked from a cygwin window, the cygwin version is found even if your cygwin/bin directory is later on the path. </p>
+<p>Alternatively, Windows users can set file permissions in Windows Explorer. (Right-click on the top-level folder & select Properties. Select the Security tab. Click Advanced. Remove all instances of Read & Execute from the Permission Entries. Click "Reset permissions on all child objects and enable propogations of inheritable permissions". Click Apply. OK. OK.) You will have to do this again when you do a clean checkout to a new directory. </p>
+<a id="bottom"></a>
</section>
</body>
</document>