[l10n] Translation status report for trunk r1229467

2012-01-09 Thread Subversion Translation Status
Translation status report for trunk@r1229467 lang trans untrans fuzzy obs -- de2081 190 307 270 UUooo es2007 264 384 404 ++UUU~ fr2269 2

Re: svn lock ends with an error E000001: Can't set permissions on '..../test.svn/db': Operation not permitted

2012-01-09 Thread Philip Martin
Paweł Sikora writes: > this is a repost of email from users@ mailinglist: > http://mail-archives.apache.org/mod_mbox/subversion-users/201112.mbox/%3C2181986.bgZxfRHeUs%40pawels%3E > > looks like regression from svn-1.6.x. Yes, fixed by r1229252. -- uberSVN: Apache Subversion Made Easy http://w

Re: svn lock ends with an error E000001: Can't set permissions on '..../test.svn/db': Operation not permitted

2012-01-09 Thread Daniel Shahaf
http://svn.haxx.se/users/archive-2008-12/0288.shtml Feel free to ping the thread on users@, though. (I've also marked it as unread in my mailbox, so I might get to it.) On Sun, Jan 8, 2012, at 18:53, Paweł Sikora wrote: > hi, > > this is a repost of email from users@ mailinglist: > http://mail

svn lock ends with an error E000001: Can't set permissions on '..../test.svn/db': Operation not permitted

2012-01-09 Thread Paweł Sikora
hi, this is a repost of email from users@ mailinglist: http://mail-archives.apache.org/mod_mbox/subversion-users/201112.mbox/%3C2181986.bgZxfRHeUs%40pawels%3E looks like regression from svn-1.6.x. BR, Paweł. please CC me on reply.

svn branching/merging regression.

2012-01-09 Thread Paweł Sikora
Hi, i've noticed that a new subversion-1.7.2 can't reintegrate a trivial branch. attached script produces on svn-1.5.2 following correct results: $ ./merge-test.sh + export LANG=C + pwd + readlink -m /home/users/pluto + here=/home/users/pluto + rm -rf repo.svn repo.svn.wc repo.git + svnadmin cre

Re: file_handle_cache branch ready for review

2012-01-09 Thread Julian Foad
Hyrum K Wright wrote: > Branko Čibej wrote: >> On 09.01.2012 14:56, Hyrum K Wright wrote: >>> Until we can change the minimum required version of APR, it just >>> isn't worth the hassle. >> [...] >> For something like the filehandle cache, which is not a functional >> requirement, we can the

Re: file_handle_cache branch ready for review

2012-01-09 Thread Hyrum K Wright
On Mon, Jan 9, 2012 at 8:37 AM, Branko Čibej wrote: > On 09.01.2012 14:56, Hyrum K Wright wrote: >> Until we can change the minimum required version of APR, it just isn't >> worth the hassle. -Hyrum > > We can change the minimum required version of APR any time we want, > really. Our API versionin

Re: Crash when updating

2012-01-09 Thread Paul Burba
On Thu, Jan 5, 2012 at 2:37 PM, Stefan Küng wrote: > Hi, > > From a crash report dump sent for TSVN for an update the attached stack > trace happened. > > libsvn_wc\props.c, svn_wc__merge_props() >      to_val = incoming_change->value >        ? svn_string_dup(incoming_change->value, result_pool)

Re: file_handle_cache branch ready for review

2012-01-09 Thread Branko Čibej
On 09.01.2012 14:56, Hyrum K Wright wrote: > Until we can change the minimum required version of APR, it just isn't > worth the hassle. -Hyrum We can change the minimum required version of APR any time we want, really. Our API versioning guidelines aren't /that/ set in stone. Sure, we'd have to a

Re: file_handle_cache branch ready for review

2012-01-09 Thread Hyrum K Wright
On Mon, Jan 9, 2012 at 2:55 AM, Julian Foad wrote: > Stefan Fuhrmann wrote: > >> Ivan Zhakov wrote: >>>    In your branch your introduce handles to handles. >>> APR does the same. Is that unreasonable? >>>  4. It seems current implementation reuses file handles even error is >>>  occurred when wor

Re: format of svn:author

2012-01-09 Thread Julian Foad
Mark Mielke wrote: > Stefan Fuhrmann wrote: >> On 04.01.2012 19:42, Julian Foad wrote: >>>     The extended author fields are delivered through revision >>> properties [that] are readable but not writable by clients. >> >> Maybe, I missed something in your post but I want >> to stress that is

Implicit keep-alive after reintegrate merge

2012-01-09 Thread Julian Foad
Merging would be simpler if the user didn't have to think about doing the "keep-alive dance" after a reintegrate [1]. I'm trying to teach the sync merge to detect when a reintegrate has been done, so that we could avoid the need for r45 in the following typical sequence: | Rev  Branch Commit |

Re: file_handle_cache branch ready for review

2012-01-09 Thread Julian Foad
Stefan Fuhrmann wrote: > Ivan Zhakov wrote: >>   In your branch your introduce handles to handles. >> APR does the same. Is that unreasonable? >> 4. It seems current implementation reuses file handles even error is >> occurred when working with the handle. It's potentially dangerous from >> my