Open
Conversation
Owner
|
This is the intended logic: branch of gef-extras should work at parity with gef. gef is considered the source of truth always, not gef-extras. When you say "The version of gef and gef-extra are not marching", what problem are having exactly? |
Author
|
gef latest version is 2026.01 while gef-extra latest version 2025.01. When fetching gef version the git clone will fail since the version 2026.01 doesn't exist in gef-extra. |
Owner
Good catch, I will publish a new release of |
Owner
|
Done |
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
2 participants
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.
Description
The version of gef and gef-extra are not marching, which causing issue while downloading from scripts/gef-extras.sh
Changing the isntall script to fetch the tag from gef-extras github repository .