Re: svn commit: r979002 - in /subversion/branches/svnrload/subversion/svnrload: ./ load_editor.c load_editor.h parse_dumpstream.c svnrload.c

artag...@apache.org wrote on Sun, 25 Jul 2010 at 11:44 -: > Author: artagnon > Date: Sun Jul 25 08:44:21 2010 > New Revision: 979002 > > URL: http://svn.apache.org/viewvc?rev=979002&view=rev > Log: > Add svnrload: currently a heavy WIP, with most of the code imported > from svnrdump > > * sub

Re: svn commit: r979002 - in /subversion/branches/svnrload/subversion/svnrload: ./ load_editor.c load_editor.h parse_dumpstream.c svnrload.c

Hi Daniel, Daniel Shahaf writes: > i.e., you could have done 'svn cp ../svnrdump/svnrdump.c svnrload.c', > and similarly for the other files. The benefits of this would be > reviewability (the diff would be far shorter than the current 1533 > lines) and historical linkage (future 'svn log', and o

Re: svn commit: r979011 - in /subversion/branches/svnrload: build.conf subversion/svnrload/ subversion/svnrload/load_editor.c subversion/svnrload/parse_dumpstream.c subversion/svnrload/svnrload.c

artag...@apache.org wrote on Sun, 25 Jul 2010 at 12:21 -: > Author: artagnon > Date: Sun Jul 25 09:20:55 2010 > New Revision: 979011 > > URL: http://svn.apache.org/viewvc?rev=979011&view=rev > Log: > Add a build.conf and get svnrload to build > > * build.conf > (svnrdump): Add new section t

Re: svn commit: r979002 - in /subversion/branches/svnrload/subversion/svnrload: ./ load_editor.c load_editor.h parse_dumpstream.c svnrload.c

Doing the work on trunk or on a branch is orthogonal to my point. Ramkumar Ramachandra wrote on Sun, 25 Jul 2010 at 16:02 -: > Hi Daniel, > > Daniel Shahaf writes: > > i.e., you could have done 'svn cp ../svnrdump/svnrdump.c svnrload.c', > > and similarly for the other files. The benefits of

Re: svn commit: r979011 - in /subversion/branches/svnrload: build.conf subversion/svnrload/ subversion/svnrload/load_editor.c subversion/svnrload/parse_dumpstream.c subversion/svnrload/svnrload.c

Hi Daniel, Daniel Shahaf writes: > Please don't mix whitespace/indentation changes and semantic changes in > the same commit. > > (I'm sure HACKING says that --- doesn't it?) Afaik, no. It says is "A patch submission should contain one logical change; please don't mix N unrelated changes in one

Re: svn commit: r979002 - in /subversion/branches/svnrload/subversion/svnrload: ./ load_editor.c load_editor.h parse_dumpstream.c svnrload.c

Hi Daniel, Daniel Shahaf writes: > Doing the work on trunk or on a branch is orthogonal to my point. Yeah, I understand. I'm just pointing out that I forgot to mark the commits as "Don't review". I'll get some reviewable changes into trunk in a few minutes. -- Ram

Re: sasl mechanisms order

CC += dev@ Victor Sudakov wrote on Mon, Jul 26, 2010 at 12:53:44 +0700: > Daniel Shahaf wrote: > > > > > > I have the following line in /usr/local/lib/sasl2/svn.conf: > > > mech_list: gssapi digest-md5 anonymous > > > > > > How can I guarantee that the subversion client/server will always use >