Re: SVN-4530 describes a really nasty bug in our command-line parsing

On 28.10.2018 01:57, Daniel Shahaf wrote: > Branko Čibej wrote on Sat, 27 Oct 2018 23:19 +0200: >> $ touch wc/foo/@bar >> $ svn add wc/foo/@bar >> svn: E29: 'wc/foo@bar': a peg revision is not allowed here >> >> Oh really? Since when are we allowed to ignore directory separators in >> paths? >

Re: SVN-4530 describes a really nasty bug in our command-line parsing

Branko Čibej wrote on Sat, 27 Oct 2018 23:19 +0200: > $ touch wc/foo/@bar > $ svn add wc/foo/@bar > svn: E29: 'wc/foo@bar': a peg revision is not allowed here > > Oh really? Since when are we allowed to ignore directory separators in > paths? wc/foo/@bar is parsed as path="wc/foo/", peg="bar"

Re: SVN-4530 describes a really nasty bug in our command-line parsing

On Sat, Oct 27, 2018 at 11:19:10PM +0200, Branko Čibej wrote: > First, read this: https://issues.apache.org/jira/browse/SVN-4530 > > Then watch this (hold my beer): > > $ svnadmin create repo > $ svn co file://$(pwd)/repo wc > Checked out revision 0. > $ svn mkdir wc/foo > A wc/foo > $ to

SVN-4530 describes a really nasty bug in our command-line parsing

First, read this: https://issues.apache.org/jira/browse/SVN-4530 Then watch this (hold my beer): $ svnadmin create repo $ svn co file://$(pwd)/repo wc Checked out revision 0. $ svn mkdir wc/foo A wc/foo $ touch wc/foo/@bar $ svn add wc/foo/@bar svn: E29: 'wc/foo@bar': a peg revision i

Re: The future of the Subversion book

On 18.10.2018 20:40, Branko Čibej wrote: > On 06.09.2018 15:25, Branko Čibej wrote: >> On 06.09.2018 15:10, C. Michael Pilato wrote: >>> On 09/05/2018 04:49 PM, Mark Phippard wrote: Assuming the PMC wanted it, is it possible for the book to be contributed to this project and hosted in the

Issue cleanup

FYI, I'm moving all our issues that are resolved and haven't been changed since 1st January to the "closed" state. There were almost 4k of them. -- Brane