course).
Thank you all for the discussion.
Greetings,
Julian
-Ursprüngliche Nachricht-
Von: Johan Corveleyn [mailto:jcor...@gmail.com]
Gesendet: Montag, 25. Juni 2012 20:54
An: Bert Huijben
Cc: Ruhe Julian; Stephen Butler; Daniel Shahaf; users@subversion.apache.org
Betreff: Re: Issue:
renamed, copied, or both. Or in other words: If -rHEAD path@peg gives
me an error, object is dead or immutable for projects already referencing it
respectively. Period.
Thank you for your patience.
Greetings,
Julian
-Ursprüngliche Nachricht-
Von: Les Mikesell [mailto:lesmikes...@gma
. Similar to the result of "svn checkout
-rHEAD path@peg". Why should svn:externals behave differently here?
Greetings,
Julian
-Ursprüngliche Nachricht-
Von: Les Mikesell [mailto:lesmikes...@gmail.com]
Gesendet: Freitag, 22. Juni 2012 14:55
An: Stephen Butler
Cc: Ruhe Julian;
Hello Daniel,
>The update command accepts -rHEAD, but not necessarily -rHEAD plus peg
>revision. HEAD is a keyword for "latest in the repository", not "latest in
>the history of URL@REV". If an item has been deleted, it's no longer part of
>the >HEAD, as you've seen.
That is not the point. I
he user will not have the chance to call any
svn command at all.
I think my use case is not completely remote. I hope I can create an issue for
it.
Greetings,
Julian
-Ursprüngliche Nachricht-
Von: Daniel Shahaf [mailto:d...@daniel.shahaf.name]
Gesendet: Freitag, 22. Juni 2012 01:47
An
Hello,
try to assign a file p.txt containing the following lines as svn:external
-r110 ^/mapping_services/global/testing/full_test/globalresource5.xml@110
"xml/globalresource5.xml"
-r84 ^/mapping_services/global/testing/full_test/globalresource4.xml@84
"xml/globalresource4_renamed.xml"
-r83 ^/m
