On 2023-06-17 16:32, Daniel Sahlberg wrote:
Den fre 16 juni 2023 kl 09:49 skrev Osipov, Michael (SMD IT IN) via
users <us...@subversion.apache.org <mailto:us...@subversion.apache.org>>:
Scratch that. My thread from five years ago is still valid:
https://lists.apache.org/thread/lonftwtj2kmnjf5mlp91jyxz9xlsgv3d
<https://lists.apache.org/thread/lonftwtj2kmnjf5mlp91jyxz9xlsgv3d>
The issue sill persists. The doc improvement from Daniel Shahaf haven't
been implemented yet.
Moving the discussion to dev@:
Do we want to implement the suggested doc improvement? I started testing
each of the commands and the @ trick is required on almost all except
for svn checkout so it will be a lot of changed text. Does it make sense
or will it only be a cause of confusion?
I added the explanation as a separate text to allow for some re-use but
the argument has many different names (PATH, WCPATH, URL ...) so it is
repeated a few times, maybe it can be reworded to leave out the argument
name?
From a user's perspective this does not make sense at all:
osipovmi@deblndw011x:~/var/Projekte/Playground
$ echo foo > m...@apache.org
osipovmi@deblndw011x:~/var/Projekte/Playground
$ LC_ALL=C svn add m...@apache.org
svn: E200009: 'm...@apache.org': a peg revision is not allowed here
I would really expect that the peg rev would used where it makes sense
and not on local paths at all.
Here [1] is a list of commands I had to modify for Maven SCM Subversion
Provider back then.
Michael
[1]
https://github.com/apache/maven-scm/commit/66a260a9107b6cec0c4ebfb9a42e9cc808512e90?w=1
