[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: James McCoy <jamessan_at_jamessan.com>
Date: Sat, 27 Oct 2018 19:56:28 -0400

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
> $ touch wc/foo/@bar
> $ svn add wc/foo/@bar
> svn: E200009: 'wc/foo_at_bar': a peg revision is not allowed here
> Oh really? Since when are we allowed to ignore directory separators in
> paths? And why the blazes would 'svn add' ever look for the peg revision
> tag?

Is it generic code handling the peg revision and then once that gets
processed, wc/foo/ is normalized to wc/foo? Seems like it since "svn
add wc/foo/@bar@" works.


GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB
Received on 2018-10-28 01:56:42 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.