Re: Adressing of below repository root in command line?

bar is the repos URL of the path foo/bar below the current directory in the working copy mean otherwise? Alrighty then, Thomas -- Dr. Thomas Orgis HPC @ Universität Hamburg

Re: Adressing of below repository root in command line?

to avoid ^/ at the beginning of any argument that is suppoed to refer to a local path. This would extend to ^./ syntax, that one would need to address an actual local directory via ./^./. Alrighty then, Thomas -- Dr. Thomas Orgis HPC @ Universität Hamburg

Adressing of below repository root in command line?

fo | grep ^Relative\ URL:| cut -f 3- -d ' ')"/foo/bar baz/flu Well … I can define that as command or shell function … but ^^ is still a lot nicer to type than $(svnrelpath). Alrighty then, Thomas -- Dr. Thomas Orgis HPC @ Universität Hamburg

Re: segfault of svn 1.14.5 in uri_escape(), called by conflict_tree_get_details_local_missing() with NULL argument

patch fixes the crash. I might want to avoid that particular merge, anyway … lots of tree conflicts for the little patch snippets … but svn is fine, now. Alrighty then, Thomas -- Dr. Thomas Orgis HPC @ Universität Hamburg

segfault of svn 1.14.5 in uri_escape(), called by conflict_tree_get_details_local_missing() with NULL argument

t work is necessary on the build system, even for something innocent as requiring a minimum version that is too minimal. Also have fun with bisecting builds, where you may need older cmake versions around or older releases. PPS: Sorry again for hijacking my own thread. I could write an even longer essay about what irks me about CMake practices, and maybe of development practices of scientific sofware in particular, which often is intermittend abandonware by definition (of the employment structure of scientists). No need to lengthy replies. Just wanted to give my perspective and a little warning. -- Dr. Thomas Orgis HPC @ Universität Hamburg

Re: More flexible support for working with partial checkouts, svn rm --keep-remote?

=exclude is effectively what I thought rm --keep-remote would do. Thanks a lot! So the tools are there, I can do some nice wrapper scripts. Alrighty then, Thomas -- Dr. Thomas Orgis Universität Hamburg Regionales Rechenzentrum / Regional Computing Center Basis-Infrastruktur / Basic Infrastruc

More flexible support for working with partial checkouts, svn rm --keep-remote?

y noise for my setup, and also I do not want to encourage actual divergence of the versioned contents, only give each working copy its selection of parts of the tree. Alrighty then, Thomas -- Dr. Thomas Orgis HPC @ Universität Hamburg

Re: Streamlining Subversion patch releases

t is just that this would differ from the simplest common case of one upstream source archive that is extracted and built. Alrighty then, Thomas -- Dr. Thomas Orgis HPC @ Universität Hamburg

Re: A strong WTF on compiling out plaintext password support by default?!

it would be a nice feature to be able review/sign those afterwards. But back on topic: Yes, please make use of simple password storage usable for everyone again. The use cases are real. Alrighty then, Thomas -- Dr. Thomas Orgis HPC @ Universität Hamburg

Re: A strong WTF on compiling out plaintext password support by default?!

could just define one by convention?). I keep using it for existing projects but feel increasingly stupid for doing so, despite my opinion of the file tree semantics being superior to branching/tagging elsewhere. Alrighty then, Thomas -- Dr. Thomas Orgis HPC @ Universität Hamburg

SVN-4845: Avoid partial commits that break mergeinfo

- Dr. Thomas Orgis HPC @ Universität Hamburg

SVN-4844: Avoid copies in mixed-revision working copies by default and add --allow-mixed-revisions for copy

we can quickly come up with a patch avoiding the creation of the ‘bad’ copies … but maybe the discussion also produces a change that makes the bogus tree conflict disappear for existing repositories. Alrighty then, Thomas -- Dr. Thomas Orgis HPC @ Universität Hamburg

Re: Handling of unexpectedly changed kind, accepting local changes in versioning changes by external forces

. It's not what I remember, but something to look at. Thanks for the pointer. Would help if it'd be contained in standard installs of svn, but I could roll it out on the servers. It reminds me of these idle ideas to have signed commits via added svn properties … Alrighty then, Thomas -- Dr. Thomas Orgis HPC @ Universität Hamburg

Handling of unexpectedly changed kind, accepting local changes in versioning changes by external forces

svn to version whole filesystems including special/device files, but cannot find it right now. I still do think that exploiting the file system metaphor of svn provides the niche for it to continue to exist besides the all-mighty git. -- Dr. Thomas Orgis HPC @ Universität Hamburg dirfile.