QUESTION
Is it possible to retroactively convert a "disjoint" working copy
into a "sparse" working copy?
===
SUMMARY
===
I have not been able to do this, and a new feature request may be
to add an "include" option to the --set-depth flag. The --set-depth
flag already ha
On Wed, Aug 15, 2012 at 7:52 AM, Philip Martin wrote:
> I'm happy to announce the release of Apache Subversion 1.7.6.
> Please choose the mirror closest to you by visiting:
>
> http://subversion.apache.org/download/#recommended-release
Cool. I'm poking at getting a 1.7.6 SRPM set up for it. I
Ok, I got it...thanks for your help
-Original Message-
From: Daniel Shahaf [mailto:d...@daniel.shahaf.name]
Sent: Wednesday, August 15, 2012 9:12 AM
To: Ferreira, Matthew
Cc: users@subversion.apache.org
Subject: Re: Issues compiling SVN 1.7.5 on Solaris Sparc 9
Build from a tarball, not
Build from a tarball, not from a tag. The latter requires Python.
Ferreira, Matthew wrote on Wed, Aug 15, 2012 at 08:59:01 -0400:
> Thxdid that , ran in to some errors...realised it was half way through
> the previous compile, so started fresh, remade config with flags, ran the
> make proce
Thxdid that , ran in to some errors...realised it was half way through the
previous compile, so started fresh, remade config with flags, ran the make
process, hit the following:
/bin/bash /tmp/svn_src/subversion-1.7.5/libtool --tag=CC --silent
--mode=compile gcc -DSOLARIS2=9 -D_POSIX_PTHREA
I'm happy to announce the release of Apache Subversion 1.7.6.
Please choose the mirror closest to you by visiting:
http://subversion.apache.org/download/#recommended-release
The SHA1 checksums are:
5b76a9f49e2c4bf064041a7d6b1bfcc3aa4ed068 subversion-1.7.6.tar.bz2
c6332c4d70685f903020
Hello,
Am 15.08.2012 13:35, schrieb Philip Martin:
There was a bug that caused unlock to leave the files:
http://subversion.tigris.org/issues/show_bug.cgi?id=3667
It is fixed in 1.6.13 but the files will remain until a suitable new
lock/unlock causes them to be deleted.
Thank you for this hint
"rog7...@web.de" writes:
> Hello Daniel,
>
> Am 11.08.2012 00:29, schrieb Daniel Shahaf:
>> If you lock /foo/bar/baz then db/locks/${hash} files are created for each of
>> / ,
>> /foo , /foo/bar .
>>
>> Consequently, if (a) there are no locks in the repository, and (b) no
>> locks are being add
Hello Daniel,
Am 11.08.2012 00:29, schrieb Daniel Shahaf:
If you lock /foo/bar/baz then db/locks/${hash} files are created for each of / ,
/foo , /foo/bar .
Consequently, if (a) there are no locks in the repository, and (b) no
locks are being added or deleted (eg: the server is in read-only mo
Mark Bober writes:
> What's the current wisdom on doing checkouts to NFS and CIFS?
>
> I'm seeing general checkout times of a given repository in the 2
> second range for local disk, and that jumps all the way up to a minute
> and a half or more going over CIFS or NFS (Windows 2008R2 fileserver,
10 matches
Mail list logo