[DO NOT MERGE] Add --unshallow to git fetch in update.sh#1234
Closed
nak3 wants to merge 1 commit intolibressl:masterfrom
Closed
[DO NOT MERGE] Add --unshallow to git fetch in update.sh#1234nak3 wants to merge 1 commit intolibressl:masterfrom
--unshallow to git fetch in update.sh#1234nak3 wants to merge 1 commit intolibressl:masterfrom
Conversation
When the openbsd repository is cloned with --depth, it becomes a shallow clone and lacks sufficient history to resolve commits based on timestamps. Replace git fetch with git fetch --unshallow to ensure the full commit history and branch are available. Fix libressl#1233
nak3
changed the title
--unshallow to git fetch in update.sh--unshallow to git fetch in update.sh
Member
Author
|
I think there are other solutions such as:
|
Member
Author
|
Closing as #1235 is a better fix. |
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
1 participant
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.
When the openbsd repository is cloned with
--depth, it becomes a shallow clone and lacks sufficient history to resolve commits based on timestamps.Replace git fetch with git fetch --unshallow to ensure the commit history and branch are available.
Fix #1233