Am Thu, 21 Nov 2024 06:32:01 -0500 schrieb Nathan Hartman <hartman.nat...@gmail.com>:
> copy --parents' is the logical equivalent of running 'svn mkdir' to create > each missing directory along the way, the same as if you created them > manually. Yes, I understand that is follows a certain logic. But, coming not from copy and mkdir as local operations, but from `svn up` as operation that brings (part of) my working copy in sync with the repo, it looks like --parents could mean to also just 'up' the (empty) parent directories, not mkdir them. I think one could argue for both interpretations of --parents triggering local creates or checkouts. But of course since there is existing behaviour, it is what it is. > But here's a suggestion: if this is a workflow you do often enough, you > could implement a script that performs these actions? Perhaps there are > additional repetitive steps you could automate? Sure, I need to write some scripts, anyway, to help colleagues who don't know svn syntax or even the need for it well enough. > There is 'svn update --set-depth=exclude foo' which will exclude foo from > your working copy (i.e., delete foo from your disk without affecting the > repository). It sounds like that is what you're looking for. Indeed! So this is a 'dumb user question' after all! I wanted to despair after seeing that the --set-depth=empty choice still leaves the directory itself there, but --set-depth=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 Infrastructure High-Performance Computing Schlüterstr. 70 20146 Hamburg Tel.: +49 40 42838 8826 E-Mail: thomas.or...@uni-hamburg.de Team: h...@uni-hamburg.de https://www.uni-hamburg.de https://www.rrz.uni-hamburg.de
smime.p7s
Description: S/MIME cryptographic signature
