Re: Feature Request: svn upgrade [--check][--check-current]

2016-12-03 Thread Daniel Shahaf
Marc Pawlowsky wrote on Fri, Dec 02, 2016 at 20:48:16 -0500: > However I believe a supported, documented, and forward compatible way is > preferable; given the volume of questions that come up when googling it > seems to be a popular item. > I don't recall it ever being asked before on this lis

Re: Feature Request: svn upgrade [--check][--check-current]

2016-12-02 Thread Marc Pawlowsky
I had found some of the magic formulas before, which was how I was aware of looking into the .svn directory. Thank you for the detailed responses which I can wrap into local commands, and should be sufficient for my needs. However I believe a supported, documented, and forward compatible way is

Re: Feature Request: svn upgrade [--check][--check-current]

2016-12-02 Thread Daniel Shahaf
Marc Pawlowsky wrote on Fri, Dec 02, 2016 at 11:50:14 -0500: > There is a lot of effort and hacks on determining what SVN database > version is being used on the working copy. Usually resorting to > examining the internal contents of a .svn/* file. The incantation is: format_number=`head -n1

Feature Request: svn upgrade [--check][--check-current]

2016-12-02 Thread Marc Pawlowsky
There is a lot of effort and hacks on determining what SVN database version is being used on the working copy. Usually resorting to examining the internal contents of a .svn/* file. For future releases it would be nice if there was a command to display if the current working copy is at the same l