Re: svn commit: r1431279 - /subversion/trunk/subversion/libsvn_wc/wc_db_util.c

2013-01-10 Thread Philip Martin
Philip Martin writes: > The WC layer has a clear distinction between create and open so fixing > in the WC layer only adds an overhead to checkout, the other operations > are unaffected. The other user is FSFS and it does not have this > distinction so the overhead would apply to all operations.

Re: svn commit: r1431279 - /subversion/trunk/subversion/libsvn_wc/wc_db_util.c

2013-01-10 Thread Philip Martin
Julian Foad writes: > Philip Martin wrote: > >> URL: http://svn.apache.org/viewvc?rev=1431279&view=rev > >> Log: >> Ensure wc.db has the permissions allowed by umask. > > ... in order to be consistent with the other files we write, > and to fix sharing a WC? > > If this bug was breaking sharing a

RE: svn commit: r1431279 - /subversion/trunk/subversion/libsvn_wc/wc_db_util.c

2013-01-10 Thread Bert Huijben
> -Original Message- > From: Branko Čibej [mailto:br...@wandisco.com] > Sent: donderdag 10 januari 2013 14:33 > To: dev@subversion.apache.org > Subject: Re: svn commit: r1431279 - > /subversion/trunk/subversion/libsvn_wc/wc_db_util.c > > On 10.01.2013 14:23, Juli

Re: svn commit: r1431279 - /subversion/trunk/subversion/libsvn_wc/wc_db_util.c

2013-01-10 Thread Branko Čibej
On 10.01.2013 14:23, Julian Foad wrote: > If we consider this to be a fix for the way SQLite behaves, do we want the > same throughout Subversion? Move the fix into svn_sqlite__open()? Only when creating a new database. > File a bug report with SQLite project? SQLite has a bug related to permi

Re: svn commit: r1431279 - /subversion/trunk/subversion/libsvn_wc/wc_db_util.c

2013-01-10 Thread Julian Foad
Philip Martin wrote: > URL: http://svn.apache.org/viewvc?rev=1431279&view=rev > Log: > Ensure wc.db has the permissions allowed by umask. ... in order to be consistent with the other files we write, and to fix sharing a WC? If this bug was breaking sharing a WC, should we back-port this fix? >