AW: duplicate externals cause update error -- thoughts?

Hi, Neels, Von: Neels J Hofmeyr [mailto:ne...@elego.de] > > I've created a check during 'svn propset' that refuses to save > svn:externals props that contain the same target more than once. The > result is an error, same as with any other externals format violations. > (#4227) > > Turns out the

Re: [RFC] svn propset should require 'force' to set unknown svn: propnames

On Sun, Nov 18, 2012 at 9:50 PM, Julian Foad wrote: > 'svn propset' lets us create any property name 'svn:foo', with good reason: > we want old clients to be able to set and edit properties that only the newer > clients know about. However, there is a pitfall for unwary users: it's east > to m

Re: [RFC] svn propset should require 'force' to set unknown svn: propnames

Julian Foad wrote on Mon, Nov 19, 2012 at 02:50:46 +: > Thoughts, objections? > Another related trap is setting a revprop as a nodeprop, or vice-versa: svn commit --with-revprop=svn:eol-style=native -mm foo.c svn propset svn:log x foo.c You might want to require --force for these too

Re: svn commit: r1410679 - /subversion/trunk/subversion/svn/main.c

Ivan Zhakov wrote: > Julian Foad wrote:   svn:global-ignore >>> >>> ...s :) >> >> Yup, I made the same mistake that I had just fixed in the previous commit >> :-) >> >> Already noticed and fixed. >> > That's why I suggested to drop this 's'. I'll bet it will be > typical typo :) Thi

[RFC] svn propset should require 'force' to set unknown svn: propnames

'svn propset' lets us create any property name 'svn:foo', with good reason: we want old clients to be able to set and edit properties that only the newer clients know about.  However, there is a pitfall for unwary users: it's east to mis-spell a prop name and not notice.  For example:   svn:ign

[svnbench] Revision: 1411034 compiled Nov 19 2012, 00:21:55 on x86_64-unknown-linux-gnu

1.7.0@1181106 vs. trunk@1411016 Started at Mon Nov 19 00:25:22 UTC 2012 *DISCLAIMER* - This tests only file://-URL access on a GNU/Linux VM. This is intended to measure changes in performance of the local working copy layer, *only*. These results are *not* generally true for everyone. Charts of t

Some FSFS repo stats

Hi there, For those of you that are facts and numbers crazy, I attached some data size info for 3 large FSFS repositories. They are 1.8-format mirrors of the Apache, KDE and wordpress repositories. I used my new fsfs-stats tool to extract the info. Some of my findings: * Apache: lots of large zi

Re: Svnserve and svnadmin

On 18.11.2012 21:20, Gianluigi wrote: > Hi, > I'm struggling with svnkit and I've any questions for you: > 1) SVNKit implemnt an svnserve or like? > 2) If don't implement, is it possible to manage a exsiting svnserve with the > svnkit API? > 3)SVNKit implement all features of svnadmin with jsvnadmi

Re: Svnserve and svnadmin

On Sun, Nov 18, 2012 at 9:20 PM, Gianluigi wrote: > Hi, > I'm struggling with svnkit and I've any questions for you: > 1) SVNKit implemnt an svnserve or like? > 2) If don't implement, is it possible to manage a exsiting svnserve with the > svnkit API? > 3)SVNKit implement all features of svnadmin

Svnserve and svnadmin

Hi, I'm struggling with svnkit and I've any questions for you: 1) SVNKit implemnt an svnserve or like? 2) If don't implement, is it possible to manage a exsiting svnserve with the svnkit API? 3)SVNKit implement all features of svnadmin with jsvnadmin? Thanks! -- View this message in context: h

Re: Did my commit credentials get lost in the Apache move?

On Nov 18, 2012 11:08 AM, "Daniel Shahaf" wrote: > > Eric S. Raymond wrote on Sun, Nov 18, 2012 at 10:43:14 -0500: > > When attempting to commit some improvements to my svncutter script in contrib: > > > > You have an apache.org account, it is independent of any tigris or > svn.collab.net account

Re: Did my commit credentials get lost in the Apache move?

Eric S. Raymond wrote on Sun, Nov 18, 2012 at 10:43:14 -0500: > When attempting to commit some improvements to my svncutter script in contrib: > You have an apache.org account, it is independent of any tigris or svn.collab.net account you may have. If you don't recall your password use https://i

Did my commit credentials get lost in the Apache move?

When attempting to commit some improvements to my svncutter script in contrib: WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-n1BmhX/pkcs11: No such file or directory Authentication realm: ASF Committers Password for 'esr': Authentication realm: