Have --catch-up=SESSION add the new hash files to SESSION#5966
Open
magnumripper wants to merge 1 commit intoopenwall:bleeding-jumbofrom
Open
Have --catch-up=SESSION add the new hash files to SESSION#5966magnumripper wants to merge 1 commit intoopenwall:bleeding-jumbofrom
magnumripper wants to merge 1 commit intoopenwall:bleeding-jumbofrom
Conversation
583cdd4 to
f379506
Compare
Member
Author
|
This is tested in all relevant ways I could think of, such as with |
f379506 to
6b3cdd9
Compare
After the --catch-up=SESSION run caught up, its input files are now added to SESSION's recovery file so that it can simply be resumed for continuing with its old files as well as the new ones. This can be disabled with a new --no-catch-up-add option.
6b3cdd9 to
b3f441c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
After the --catch-up=SESSION run finished, add its input files to SESSION's recovery file so that SESSION can simply be resumed for continuing with its old files as well as the new ones.
This can be disabled with a new --no-catch-up-add option.