Re: svn commit: r1448847 - in /subversion/site: ./ publish/docs/community-guide/

2013-02-21 Thread Gabriela Gibson
On 21/02/13 23:18, Daniel Shahaf wrote: On Thu, Feb 21, 2013 at 11:12:27PM -, g...@apache.org wrote: Patch by: Gabriela Gibson Also, please add an "Approved by: danielsh" tag, and add yourself to trunk/COMMITTERS. Almost all done(rest happens tomorrow), thank you very much for all the h

Re: Merge conflicts and mergeinfo graph problems with FSFS format7 branch [was: FSFS format7 status and first results]

2013-02-21 Thread Branko Čibej
On 21.02.2013 19:15, Mark Phippard wrote: > On Thu, Feb 21, 2013 at 1:04 PM, Mark Phippard wrote: > >>> That graph is wrong or at least misleading. There have been catch-up >>> merges, for example this one: >>> I don't yet know what's going wrong, but likely something to do with >>> subtree mer

Re: [RFC] Build System Documentation

2013-02-21 Thread Daniel Shahaf
(sorry for the delay) Gabriela Gibson wrote on Mon, Feb 18, 2013 at 12:10:50 +: > 2. Example compile > -- > > svn co https://svn.apache.org/repos/asf/subversion/trunk > cd trunk > ./get-deps.sh Note that the serf this downloads must be compiled/installed (and potentially pass

Re: svn commit: r1448847 - in /subversion/site: ./ publish/docs/community-guide/

2013-02-21 Thread Daniel Shahaf
On Thu, Feb 21, 2013 at 11:12:27PM -, g...@apache.org wrote: > Patch by: Gabriela Gibson Also, please add an "Approved by: danielsh" tag, and add yourself to trunk/COMMITTERS.

Re: svn commit: r1448847 - in /subversion/site: ./ publish/docs/community-guide/

2013-02-21 Thread Daniel Shahaf
On Thu, Feb 21, 2013 at 11:12:27PM -, g...@apache.org wrote: > Log: > [[[ > You should have removed the [[[..]]] before committing. Please fix. > Add a section to Community Guide describing procedure for obtaining > the source for the Subversion web site. Addition of navigation links > to

Re: r1442088 - Improve DAG node / path lookup performance in FSFS

2013-02-21 Thread Stefan Fuhrmann
On Mon, Feb 4, 2013 at 7:59 PM, Julian Foad wrote: > Hi Stefan. > > > URL: http://svn.apache.org/viewvc?rev=1442088&view=rev > > Log: > > Improve DAG node / path lookup performance in FSFS. Since this is a hot > > path in many fs_repo-based functions (like fs_verify), 20 .. 30% time > > saved her

Re: svn commit: r1448810 - in /subversion/trunk/subversion: include/private/svn_fs_util.h libsvn_fs_fs/tree.c libsvn_fs_util/fs-util.c

2013-02-21 Thread C. Michael Pilato
On 02/21/2013 04:32 PM, stef...@apache.org wrote: > Modified: subversion/trunk/subversion/include/private/svn_fs_util.h > URL: > http://svn.apache.org/viewvc/subversion/trunk/subversion/include/private/svn_fs_util.h?rev=1448810&r1=1448809&r2=1448810&view=diff >

Re: svn commit: r1448784 - in /subversion/trunk/subversion: libsvn_wc/node.c tests/cmdline/update_tests.py tests/libsvn_wc/op-depth-test.c

2013-02-21 Thread Philip Martin
"Bert Huijben" writes: >> -Original Message- >> From: phi...@apache.org [mailto:phi...@apache.org] >> * subversion/libsvn_wc/node.c >> (svn_wc__node_get_base): Ignore not-present nodes. > > I think you should at least tweak the documentation for this function > to handle this case. This

RE: svn commit: r1448784 - in /subversion/trunk/subversion: libsvn_wc/node.c tests/cmdline/update_tests.py tests/libsvn_wc/op-depth-test.c

2013-02-21 Thread Bert Huijben
> -Original Message- > From: phi...@apache.org [mailto:phi...@apache.org] > Sent: donderdag 21 februari 2013 20:51 > To: comm...@subversion.apache.org > Subject: svn commit: r1448784 - in /subversion/trunk/subversion: > libsvn_wc/node.c tests/cmdline/update_tests.py tests/libsvn_wc/op-dep

Re: Merge conflicts and mergeinfo graph problems with FSFS format7 branch [was: FSFS format7 status and first results]

2013-02-21 Thread Mark Phippard
On Thu, Feb 21, 2013 at 1:04 PM, Mark Phippard wrote: >> That graph is wrong or at least misleading. There have been catch-up >> merges, for example this one: > >> I don't yet know what's going wrong, but likely something to do with subtree >> mergeinfo is causing the mergeinfo >> graph to thi

Re: Merge conflicts and mergeinfo graph problems with FSFS format7 branch [was: FSFS format7 status and first results]

2013-02-21 Thread Mark Phippard
On Thu, Feb 21, 2013 at 11:54 AM, Julian Foad wrote: > Mark Phippard wrote: > >> On Thu, Feb 21, 2013 at 5:05 AM, Stefan Fuhrmann >> wrote: >> BTW, how are you managing your branch? I tried merging it back to trunk to get an idea on the diff and there were a lot of text and tree

Re: Re: [bug] detect-merge-conflicts.sh reports false positive merge conflict markers

2013-02-21 Thread Matthias Buecher / Germany
Alan, thanks for the info. I have re-tested on NetBSD 5.0, Debian 6.0, Redhat on Sourceforge, FreeBSD 9 and also on OpenWrt/Busybox 1.19.4. All sed versions support semicolon. NetBSD needs newlines after closing brackets. Busybox needs nested brackets for "p" and "q" to work correctly (also makes

Merge conflicts and mergeinfo graph problems with FSFS format7 branch [was: FSFS format7 status and first results]

2013-02-21 Thread Julian Foad
Mark Phippard wrote: > On Thu, Feb 21, 2013 at 5:05 AM, Stefan Fuhrmann > wrote: > >>> BTW, how are you managing your branch?  I tried merging it back to >>> trunk to get an idea on the diff and there were a lot of text and tree >>> conflicts.  I thought I had seen you doing synch merges from

Re: FSFS format7 status and first results

2013-02-21 Thread Mark Phippard
On Thu, Feb 21, 2013 at 5:05 AM, Stefan Fuhrmann wrote: >> BTW, how are you managing your branch? I tried merging it back to >> trunk to get an idea on the diff and there were a lot of text and tree >> conflicts. I thought I had seen you doing synch merges from trunk in >> the past so I assumed

svn cleanup no longer detects old WC formats

2013-02-21 Thread Julian Foad
We seem to have lost the nice "WC is too old ... please see 'svn upgrade'" in one place: 'svn cleanup'. $ # Create v1.6 and v1.7 WCs $ svnadmin16 create r16; svn16 co file:///`pwd`/r16 wc16 $ svnadmin17 create r17; svn17 co file:///`pwd`/r17 wc17 $ # It was working nicely with svn 1.7 $ svn17 cl

Build System: autogen.sh header warnings when compiling with gtest

2013-02-21 Thread Gabriela Gibson
Ben Reser asked me in the "[RFC] Build System Documentation thread" about the gtest example: " > -mv $GTEST gtest > +mv $GTEST libgtest > +echo "Gtest has been installed, please note:" > +echo "autogen.sh will issue spurious header warnings." > +echo "./configure --enable-gte

Re: Problem with Fedora 18

2013-02-21 Thread Celso Tadao Suzuki
Hi, I think that these question is not for me, but to the development staff. But as a user, if I got a message like these, certainly that I will look at my NFS server first, instead the of the SVN. Att. Celso Suzuki Em 21-02-2013 10:46, Stefan Sperling escreveu: On Thu, Feb 21, 2013 at 09:4

Re: Problem with Fedora 18

2013-02-21 Thread Stefan Sperling
On Thu, Feb 21, 2013 at 09:47:34AM -0300, Celso Tadao Suzuki wrote: > Hi, > > Yes, you are right again. > I ran the nfslock service and the svn is working fine now. > > Thank you for your attencion. > Perhaps we should apply a patch like this? (I haven't run the tests on it yet.) [[[ * subver

Re: Problem with Fedora 18

2013-02-21 Thread Celso Tadao Suzuki
Hi, Yes, you are right again. I ran the nfslock service and the svn is working fine now. Thank you for your attencion. Best Regards Celso Suzuki Em 21-02-2013 09:20, Philip Martin escreveu: Celso Tadao Suzuki writes: *The NFS server is a Linux box with Red Hat 5. Kernel **2.6.18-53.1.4.e

Re: Problem with Fedora 18

2013-02-21 Thread Philip Martin
Celso Tadao Suzuki writes: > *The NFS server is a Linux box with Red Hat 5. Kernel **2.6.18-53.1.4.el5PAE** > ** > **I mount with these options */*exec,dev,suid,rw,noauto*/ > stat64("/home2/celso/SVN/tcf/.svn/tmp/wcng/.svn/wc.db", 0xbfa22a58) = -1 > ENOENT (No such file or directory) > open("/h

Re: FSFS format7 status and first results

2013-02-21 Thread Stefan Fuhrmann
On Thu, Feb 21, 2013 at 12:06 PM, Johan Corveleyn wrote: > On Thu, Feb 21, 2013 at 11:05 AM, Stefan Fuhrmann > wrote: > > On Mon, Feb 18, 2013 at 5:54 PM, Mark Phippard > wrote: > >> On Sat, Feb 16, 2013 at 4:30 PM, Stefan Fuhrmann > >> wrote: > ... > >> > Quite a number of reasons: > >> > > >

Re: Problem with Fedora 18

2013-02-21 Thread Philip Martin
Celso Tadao Suzuki writes: > My directory is at a NFS FS so I could execute these test. > > Well, but even if I don't want to keep my work copy and get a new one on my > directory the same error occurs > why if there is no meta data ? > *[celso@sfw06 tcf]$ cd .. > [celso@sfw06 SVN]$ svn co

Re: FSFS format7 status and first results

2013-02-21 Thread Branko Čibej
On 21.02.2013 12:06, Johan Corveleyn wrote: > On Thu, Feb 21, 2013 at 11:05 AM, Stefan Fuhrmann > wrote: >> On Mon, Feb 18, 2013 at 5:54 PM, Mark Phippard wrote: >>> On Sat, Feb 16, 2013 at 4:30 PM, Stefan Fuhrmann >>> wrote: > ... Quite a number of reasons: * easy setup * mi

Re: Problem with Fedora 18

2013-02-21 Thread Celso Tadao Suzuki
Hi, I tried as Mr Sperling suggested. I ran tye cleanup command at a 1.6 client.* **[celso@sfw11 tcf]$ svn cleanup** **celso@svn's password: ** **Connection to svn closed.* After that I tried the upgrade command at 1.7 client. *[celso@sfw06 tcf]$ svn upgrade** **svn: E200033: database is locked,

Re: svn commit: r1442071 - in /subversion/trunk/subversion/libsvn_fs_fs: dag.c temp_serializer.c

2013-02-21 Thread Stefan Fuhrmann
On Mon, Feb 4, 2013 at 7:31 PM, Blair Zajac wrote: > On 02/04/2013 02:38 AM, stef...@apache.org wrote: > >> Author: stefan2 >> Date: Mon Feb 4 10:38:45 2013 >> New Revision: 1442071 >> >> URL: >> http://svn.apache.org/viewvc?**rev=1442071&view=rev

Re: svn commit: r1442071 - in /subversion/trunk/subversion/libsvn_fs_fs: dag.c temp_serializer.c

2013-02-21 Thread Stefan Fuhrmann
On Mon, Feb 4, 2013 at 2:02 PM, Philip Martin wrote: > stef...@apache.org writes: > > > Author: stefan2 > > Date: Mon Feb 4 10:38:45 2013 > > New Revision: 1442071 > > > > URL: http://svn.apache.org/viewvc?rev=1442071&view=rev > > Log: > > Speed up serialization of DAG and noderev structures for

Re: Problem with Fedora 18

2013-02-21 Thread Celso Tadao Suzuki
Hi, Thank you for your aswer. No, I didn't had. But no, there were no effect. *[celso@sfw06 tcf]$ svn cleanup** **svn: E155036: Please see the 'svn upgrade' command** **svn: E155036: Working copy '/home2/celso/SVN/tcf' is too old (format 10, created by Subversion 1.6)** **[celso@sfw06 tcf]$ svn

Re: FSFS format7 status and first results

2013-02-21 Thread Johan Corveleyn
On Thu, Feb 21, 2013 at 11:05 AM, Stefan Fuhrmann wrote: > On Mon, Feb 18, 2013 at 5:54 PM, Mark Phippard wrote: >> On Sat, Feb 16, 2013 at 4:30 PM, Stefan Fuhrmann >> wrote: ... >> > Quite a number of reasons: >> > >> > * easy setup >> > * minimal overhead (I want to get as close to measuring p

Re: FSFS format7 status and first results

2013-02-21 Thread Stefan Fuhrmann
On Mon, Feb 18, 2013 at 1:46 PM, Daniel Shahaf wrote: > Stefan Fuhrmann wrote on Sat, Feb 16, 2013 at 10:52:21 +0100: > > Hey all, > > > > Just to give you an update on what is going on that branch, > > here a few facts and numbers. Bottom line is that there is > > still a lot to do but the basi

Re: FSFS format7 status and first results

2013-02-21 Thread Stefan Sperling
On Thu, Feb 21, 2013 at 11:05:56AM +0100, Stefan Fuhrmann wrote: > On Mon, Feb 18, 2013 at 5:54 PM, Mark Phippard wrote: > > BTW, how are you managing your branch? I tried merging it back to > > trunk to get an idea on the diff and there were a lot of text and tree > > conflicts. I thought I had

Re: FSFS format7 status and first results

2013-02-21 Thread Stefan Fuhrmann
On Mon, Feb 18, 2013 at 5:54 PM, Mark Phippard wrote: > On Sat, Feb 16, 2013 at 4:30 PM, Stefan Fuhrmann > wrote: > > On Sat, Feb 16, 2013 at 5:47 PM, Mark Phippard > wrote: > >> > >> On Sat, Feb 16, 2013 at 4:52 AM, Stefan Fuhrmann > >> wrote: > >> > Hey all, > >> > > >> > Just to give you an

Re: Problem with Fedora 18

2013-02-21 Thread Stefan Sperling
On Wed, Feb 20, 2013 at 08:51:25PM -0500, Gavin Baumanis wrote: > Have you tried performing a; > svn cleanup of your local working copy and then the upgrade? Yes, this is recommended. Try running 'svn cleanup' with a 1.6 client, and then try running 'svn upgrade' with a 1.7 client. Keep in mind t