You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
match /trunk/
min revision 100
repository Repo
branch main
end match
which starts from min revision 100. The tool only adds the changes from revision numbers 100-1000. So is it correct that any files are missing in Repo which where introduced in revision 0-100 ?
I do that because revision number 55 is corrupt. How can I get the full state also by only importing 100-1000 ?
Do I need to pre-fill the bare Repo with all files present in revision 99 ?
Thanks a lot for a quick answer.
The text was updated successfully, but these errors were encountered:
Hi,
You need to start processing at the first revision touching the paths you are interested in.
To get around the bad revision, ignore that specific revision.
Thanks. I then use the revision file argument. Might there be the other solution to just prepare the repository with the initial stuff and start from the revision „min revision“ in the rule file. Hopefully this tool does not recreate the repository if it already exists?
Von meinem iPhone gesendet
Am 02.07.2021 um 21:03 schrieb Torgny Nyblom ***@***.***>:
Hi,
You need to start processing at the first revision touching the paths you are interested in.
To get around the bad revision, ignore that specific revision.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
If we have repo with 1000 revision and the rule
which starts from
min revision 100
. The tool only adds the changes from revision numbers 100-1000.So is it correct that any files are missing in
Repo
which where introduced in revision0-100
?I do that because revision number
55
is corrupt. How can I get the full state also by only importing 100-1000 ?Do I need to pre-fill the bare
Repo
with all files present in revision99
?Thanks a lot for a quick answer.
The text was updated successfully, but these errors were encountered: