>
>
> One of the many things I would like to do for version 2 is to find a way
> to parallelize more, so that quad core and such can be used. I'm still
> not exactly sure how is the best way to do that.
I might be wrong and it is probably not that simple (and I can't really
check right now), but
>
> You just use the tortoise SVN function that does it. Never mind, I need
> to investigate why mkdir c:\ and mkdir x:\ behave differently. Is one a
> network drive, by any chance?
No, no network drives:
for example if e: is a separate drive/partition: (Tested this on different
machines, all XP)
Julian wrote:
> Of course! Please find attached
> I'm just not sure how to create the standard "patch" file,
You just use the tortoise SVN function that does it. Never mind, I need
to investigate why mkdir c:\ and mkdir x:\ behave differently. Is one a
network drive, by any chance?
> For window
You're right david.
I used Visual Studio 2005 to compile, whilst I remember Shachar mentioning
he usually uses VC6 iirc.
Plus I have the stlport libraries actually compiled locally.
Not sure which the actual reason is, but I haven't noticed any performance
issues at all. Let me know if you notice a
Julian wrote:
>
> David:
>
> if you need the recompiled exe before Shachar releases the next
> version, I could send it to you.
>
> (PS Assuming you're using windows, otherwise i'll send you the patch)
Do feel free to send it to the list, though.
Shachar
-
>
>
> David:
>
> if you need the recompiled exe before Shachar releases the next version, I
> could send it to you.
>
(PS Assuming you're using windows, otherwise i'll send you the patch)
On 14/03/2008, David V. <[EMAIL PROTECTED]> wrote:
> >
> > I hope Sachar can reproduce the problem and then f
OK. Problem solved.
Shachar:
The problem lied within mkpath in autofd.h.
The first substring is always simply "X:" where X is the drive in question.
So CreateDirectory always tries to create the directory X:\ in the first
iteration.
If the drive is C, a simple "A subdirectory or file c: already e
