Working on some tools for a development environment that will make use
of SVN. There are circumstances where I want to create temporary
information of my own, related to checked out versions. Rather than
cluttering up the working directory with other special directories and
files, I was wonde
On Thu, Mar 6, 2014 at 5:44 PM, jrm wrote:
> Working on some tools for a development environment that will make use of
> SVN. There are circumstances where I want to create temporary information
> of my own, related to checked out versions. Rather than cluttering up the
> working directory with
On 03/06/2014 08:48 PM, Andy Levy wrote:
On Thu, Mar 6, 2014 at 5:44 PM, jrm wrote:
Working on some tools for a development environment that will make use of
SVN. There are circumstances where I want to create temporary information
of my own, related to checked out versions. Rather than clut
On 07.03.2014 17:24, jrm wrote:
>
> On 03/06/2014 08:48 PM, Andy Levy wrote:
>> On Thu, Mar 6, 2014 at 5:44 PM, jrm wrote:
>>> Working on some tools for a development environment that will make
>>> use of
>>> SVN. There are circumstances where I want to create temporary
>>> information
>>> of my
On 3/7/14, 8:24 AM, jrm wrote:
>> Do not do anything in the .svn directory. That directory is
>> exclusively for the use of the SVN working copy library and you could
>> easily break your WC.
>
> Sure - if I overwrote something that has a genuine purpose - or created
> something in a location wher
Branko Čibej writes:
> No-one can stop you from messing with .svn/, but if you do, please don't
> report here when something breaks.
Running 'svn cleanup' removes everything in .svn/tmp. Upgrading from
1.6 to 1.7 removes the entire .svn directory from every directory except
the working copy roo
On Fri, Mar 7, 2014 at 11:24 AM, jrm wrote:
> Sure - if I overwrote something that has a genuine purpose - or created
> something in a location where SVN expects exactly certain files to be.
> But is SVN so fragile that it can't tolerate a differently named
> subdirectory
> or file under there?
Branko Čibej 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 fi
On May 4, 2014, at 15:46, David Balažic wrote:
> Branko Čibej 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"
On 04.05.2014 22:46, David Balažic wrote:
> Branko Čibej 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/p
Ryan Schmidt wrote:
> On May 4, 2014, at 15:46, David Balažic wrote:
>
> > Branko Čibej 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,
> >
>
On 05.05.2014 06:56, David Balažic wrote:
> Ryan Schmidt wrote:
>> On May 4, 2014, at 15:46, David Balažic wrote:
>>
>>> Branko Čibej 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 fi
12 matches
Mail list logo
