StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>First, what do you mean <em>in Subversion</em>?</p> <p>Let's clarify this:</p> <ul> <li><p>Subversion has a place where all files and versions are stored. This is the <em>repository</em>. You never see the actual directory structure of the repository, and you probably don't have read/write access there.</p></li> <li><p>You checkout the files from the repository to your local <em>working directory</em>. The <em>working directory</em> reflects a <em>particular version</em> of the various files and directories that are stored in your Subversion repository. However, you have access to them. If you make a change in one of these and commit them, you've updated the repository.</p></li> </ul> <hr> <p>Okay, now that we have that cleared up, I'm going to make the assumption that the files you're talking about are located on your <em>local directory</em>, but not in the <em>source repository</em>. Is that correct?</p> <p>In this case, the <code>svn:ignore</code> should be on the directory where the log files sit, and should have the value "*.txt". You can do it like this:</p> <pre><code>$svn propset svn:ignore "*.txt" . </code></pre> <p>Note the use of quotes around <em>*.txt</em>. They're required in this case. What this will do is prevent new files in that directory from showing up if they match the glob pattern of your svn:ignore when you do a <code>svn status</code>. They will also not be added if you just say <code>svn add</code>:</p> <pre><code>$ svn add </code></pre> <p>However, if the files are already in the repository, the <code>svn:ignore</code> property will do nothing. If you want to remove the files from the repository, but keep them on your local disk, you can do this:</p> <pre><code>$ svn delete --keep-local (files to delete) </code></pre>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload