unfs3: 0.9.22 -> 0.10.0#182309
Merged
Conversation
Author
|
I've been using this for almost three months and haven't encountered any issues. I've asked upstream to tag a release; when they do that I will revise and undraftify this. Hopefully that happens before the 22.11 release. |
Contributor
|
0.10.0 has been tagged, but not released yet. I think we can start from here. I'll be happy to test it. |
Author
|
ZHF: #199919 |
mweinelt
reviewed
Nov 12, 2022
Co-authored-by: Martin Weinelt <mweinelt@users.noreply.github.com>
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 of changes
Unbreak
unfs3. They merged the migration tolibtirpcin 2022-May but didn't tag 0.10.0 until 2022-Oct.The sourceforge page from which we previously were downloading the source code has a
<meta http-equiv>redirect pointing tounfs3.github.io, so it is safe to assume that the migration to that particular github account was intended by whoever controlled the place from which we were previously getting the source code.I'm using this on a daily basis, although in a mostly-reads few-writes use case.
Things done
./result/bin/)