Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: domain of brane@wandisco.com designates
 74.125.82.180 as permitted sender)
Message-ID: <536712F1.2020502@wandisco.com>
Date: Mon, 05 May 2014 06:26:25 +0200
From: =?UTF-8?B?QnJhbmtvIMSMaWJlag==?= <brane@wandisco.com>
Organization: WANdisco
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
 rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: users@subversion.apache.org
Subject: Re: .svn directory - safe to add files in ".svn" or ".svn/tmp"?
References: <53192CD9.6010603@exa.com> <5319F2A8.2080104@exa.com>
 <5319F4FE.2030905@wandisco.com> <loom.20140504T224249-216@post.gmane.org>
In-Reply-To: <loom.20140504T224249-216@post.gmane.org>
Content-Type: multipart/alternative;
 boundary="------------020401030702030400060400"

This is a multi-part message in MIME format.
--------------020401030702030400060400
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

On 04.05.2014 22:46, David Balažic wrote:
> Branko Čibej <brane <at> wandisco.com> writes:
>
>>     It's not a question of SVN being fragile or not. The .svn/ directory
>>     is private to Subversion and you're not allowed to fiddle with it.
> Servus Branko,
>
> related to this, is the name ".svn" reserved/prohibited?
> What if I wanted to commit a bunch of files that would contain a file (or
> folder) named ".svn".
> With recent SVN versions, there is no .svn folder in each WC folder, so it
> would not immediately conflict.

It might not conflict, unless someone decides to check out a subset of
your repository (or define an external referring to such a subset) that
just happens to have that object called ".svn" at the root of the
checkout. So no, I would not recommend that. Happily, Subversion doesn't
allow it, either.

-- Brane


-- 
Branko Čibej | Director of Subversion
WANdisco // Non-Stop Data
e. brane@wandisco.com

--------------020401030702030400060400
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 04.05.2014 22:46, David Balažic
      wrote:<br>
    </div>
    <blockquote cite="mid:loom.20140504T224249-216@post.gmane.org"
      type="cite">
      <pre wrap="">Branko Čibej &lt;brane &lt;at&gt; wandisco.com&gt; writes:

</pre>
      <blockquote type="cite">
        <pre wrap="">    It's not a question of SVN being fragile or not. The .svn/ directory
    is private to Subversion and you're not allowed to fiddle with it.
</pre>
      </blockquote>
      <pre wrap="">
Servus Branko,

related to this, is the name ".svn" reserved/prohibited?
What if I wanted to commit a bunch of files that would contain a file (or
folder) named ".svn".
With recent SVN versions, there is no .svn folder in each WC folder, so it
would not immediately conflict.
</pre>
    </blockquote>
    <br>
    It might not conflict, unless someone decides to check out a subset
    of your repository (or define an external referring to such a
    subset) that just happens to have that object called ".svn" at the
    root of the checkout. So no, I would not recommend that. Happily,
    Subversion doesn't allow it, either.<br>
    <br>
    -- Brane<br>
    <br>
    <br>
    <div class="moz-signature">-- <br>
      <span style="font-face:sans-serif;font-size:9pt;line-height:18pt">Branko
        Čibej <span style="color: #f90">|</span> <span
          style="font-weight:bold">Director of Subversion</span>
        <br>
        WANdisco <span style="color: #f90">//</span> <span
          style="font-style:oblique">Non-Stop Data</span>
        <br>
        <span style="color: #ccc">e.</span> <a class="moz-txt-link-abbreviated" href="mailto:brane@wandisco.com">brane@wandisco.com</a></span></div>
  </body>
</html>

--------------020401030702030400060400--