Re: Sv: List modified on a branch

2022-02-17 Thread Kristofer
If you have never merged anything from trunk, you have to do the more cumbersome version with doing "log -v --stop-on-copy" to find the copy source in the last of those revisions. If you know you have merged the trunk at least once, then you have that information in the svn:mergeinfo property s

Fw: svndumpfilter: finding source commit for error?

2022-01-04 Thread Kristofer
in dump --exclude /rootDir/badDir" does the trick. Just in case anyone else runs into this, remember the initial slash On Thursday, December 9th, 2021 at 7:47 PM, Stefan Sperling wrote: > On Thu, Dec 09, 2021 at 06:29:14PM +, Kristofer wrote: > > > Hi Stefan and thanks for

Re: svndumpfilter: finding source commit for error?

2021-12-09 Thread Kristofer
lly a null operation, but it messes with things like "log --stop-on-copy" ‐‐‐ Original Message ‐‐‐ On Thursday, December 9th, 2021 at 7:08 PM, Stefan Sperling wrote: > On Thu, Dec 09, 2021 at 05:07:09PM +, Kristofer wrote: > > > And of course, soon after maili

Re: svndumpfilter: finding source commit for error?

2021-12-09 Thread Kristofer
x27;t matter at this point :) I suppose there is something with the mergeinfo that I do not understand, but since I managed to get around it, no need to bother this list further. Sorry about the noise. ‐‐‐ Original Message ‐‐‐ On Thursday, December 9th, 2021 at 4:44 PM, Kristofer wrote:

svndumpfilter: finding source commit for error?

2021-12-09 Thread Kristofer
Hi, I'm doing some work on an old, bloated repo to get rid of some erroneous commits to reduce the disk size. I've done this a few years ago with success, but I'm currently getting into an error situation that I don't know how to handle. I'm running something like "svadmin dump | svndumpfilter