On Friday, 29 July 2022 at 19:13:37 UTC+2 Stefan wrote:
> I guess all of you in this discussion thread work in a team where
everyone has checked out from the same 'root' of a repo (e.g. trunk). So
you maybe expect those commands to always use the wc root as the root of
the relative paths. But many teams don't work that way, especially those
that have >100GB working copies if checked out from trunk - in such teams
it happens that different team members have different subfolders checked
out. So there the relative path is relative to their working copies. Now
imagine person A has /trunk checked out because that person maybe also does
a full build of the project. Person B has only /trunk/subProject1 checked
out. Person A needs to send B a patch of some files in subProject1, so if
TSVN would always create the patch with paths relative to the WC root,
person B would get a patch that can't be applied because the paths would
contain /subProject1/file1.cpp, and the WC might be named subProject1-test
- so that part's wouldn't match.
In this case, person A can create the patch from subProject1 instead of the
wc root and get a patch that person B can apply.
To solve this, patching tools have an option like:
-pnum or --strip=num
Strip the smallest prefix containing num leading slashes from each file
name found in the patch file. A sequence of one or more adjacent slashes is
counted as a single slash. This controls how file names found in the patch
file are treated, in case you keep your files in a different directory than
the person who sent out the patch. For example, supposing the file name in
the patch file was
Regards,
David
--
You received this message because you are subscribed to the Google Groups
"TortoiseSVN" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to tortoisesvn+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tortoisesvn/8ce12cfc-488c-4bf6-8638-1e4d7e786120n%40googlegroups.com.
