Hello,
I have a problem with partial checkout of the repository from the boost c++
library.
First I guessed, that this is a problem with Tortoise SVN, because there
have been problems with the TSVN
cache in the past. Switching off the caching mechanism showed, that this is
not the cause of
Jason Wong wrote on Fri, Mar 30, 2012 at 11:39:02 -0700:
> On Wed, Mar 28, 2012 at 12:00 PM, Daniel Shahaf wrote:
> > Jason Wong wrote on Wed, Mar 28, 2012 at 11:49:20 -0700:
> >> dump-noderev.pl /repo /
> >> -
> >> id: 0.0.r62104/28771
> >> type: dir
> >> pred: 0.0.r62103/2868
On Wed, Mar 28, 2012 at 12:00 PM, Daniel Shahaf wrote:
> Jason Wong wrote on Wed, Mar 28, 2012 at 11:49:20 -0700:
>> dump-noderev.pl /repo /
>> -
>> id: 0.0.r62104/28771
>> type: dir
>> pred: 0.0.r62103/28680
>> count: 62071
>> text: 62104 27520 1238 1238 ea635421e867454f9f7bc5
Do you have a precommit hook now that was not there when revs 81-82
were committed?
Svn log will show the revisions whereever in the repository they were
made. Are they missing for real?
/$
On Fri, Mar 30, 2012 at 15:25, Gary wrote:
> I see a lot of reports of this error, but little in the way of
Filed http://subversion.tigris.org/issues/show_bug.cgi?id=4155
> -Original Message-
> From: Daniel Shahaf [mailto:d...@daniel.shahaf.name]
> Sent: Thursday, March 29, 2012 4:51 AM
> To: Stephen Butler
> Cc: Varnau, Steve (Seaquest R&D); users@subversion.apache.org; Brackett,
> Faye
> Subj
I see a lot of reports of this error, but little in the way of
clear information as to what it might mean, or how to fix it:
$ svnsync sync file://`pwd`/dest
Committed revision 1.
Copied properties for revision 1.
Transmitting file data .
[...]
Committed revision 79.
Copied pro
On Fri, Mar 30, 2012 at 7:53 AM, Rob Pointer wrote:
> Forgive me if I am misunderstanding here however SVN clients cannot be
> 'forward' compatible. i.e. an svn 1.4 client will not work with a 1.6
> server (repository format differs) and checking out in this manner would
> produce an error saying
2012/3/29 coolie :
> I have an inherited repo structure that has many projects with their own
> tags and branches folders.
> Users check out the whole structure as there are common lib references etc,
> but don't need to see the full contents
> of tags or branches folders, which can be massive. I w
On Fri, Mar 30, 2012 at 7:53 AM, Rob Pointer wrote:
> Forgive me if I am misunderstanding here however SVN clients cannot be
> 'forward' compatible. i.e. an svn 1.4 client will not work with a 1.6
> server (repository format differs) and checking out in this manner would
> produce an error saying
Forgive me if I am misunderstanding here however SVN clients cannot be
'forward' compatible. i.e. an svn 1.4 client will not work with a 1.6
server (repository format differs) and checking out in this manner would
produce an error saying that the expected repository format was incorrect.
However
Tom Hanstra writes:
> Now I am trying to compile subversion 1.7.4. I configure using this
> command:
>
> ./configure --prefix=/shared/svnprod/soft --with-apr=/shared/apr
> --with-apr-util=/shared/apr-util
> --with-apxs=/shared/svnprod/httpd/bin/apxs
> --with-sqlite=/shared/sqlite --with-neon=/s
11 matches
Mail list logo