Open gschwind opened 5 years ago
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Thursday, September 5, 2019 6:02 PM, gschwind notifications@github.com wrote:
For my needs I added a revision range in the filter, this mean that filter only apply for the given revision ranges, and all other files/revisions are marked as wanted.
One use case is to prune old svn revision and keep most recent revision intact.
I'm not sure this is something I'd want to include as a feature, because it could easily break the repository when svn interacts with a file or directory that comes after the specified range, yet, because of the modifications inside the range that file no longer exists.
If what you want to do is to leave the repository files as they are, but clean up the history of their creation, I would much prefer the more involved but far safer process of: 1) Sanitize the dump file normally with no ranges. 2) Import sanitized dump to new repository 3) Copy old repository files over to new repository and commit that.
Hello,
This is not exactly what I intend to do, I want keep my history from a specific revision in the past, and prune older revisions. As far as I understood, the code mask files to be kept or not, when they are kept all theirs dependency are also kept. This mean that even if I did not marked a file as wanted in my range of revision, it will be marked by following revision if they are needed. Thus If I understand well that cannot break the history, but maybe I'm wrong.
Beside that, you are free to include my change, currently I'm happy with them, I just share it if someone else need it. In any case, if I'm wrong I would like to fix it, even you don't want include it.
And thanks for this tool that is work like expected :) Best regards
Hello,
For my needs I added a revision range in the filter, this mean that filter only apply for the given revision ranges, and all other files/revisions are marked as wanted.
One use case is to prune old svn revision and keep most recent revision intact.
Best regards.