Fix references to files.gpg in FAQ #336
Closed
Conversation
This file contains 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
ericvsmith
reviewed
May 1, 2021
There was a problem hiding this comment.
Thanks for this, @rasa. I've suggested a few style changes, but feel free to ignore or modify them.
|
I made all the above suggestions in #337. I'm closing this PR as I branched off of gh-pages, instead of dev-pages. Sorry 'bout that. |
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.
Fixes #334, #335
What does this PR do?
Replaces references to
files.gpgwith~/.local/share/yadm/archive.What issues does this PR fix or reference?
#334 #335
Previous Behavior
FAQ referred to obsolete file
files.gpg.New Behavior
FAQ refers to current
~/.local/share/yadm/archivefile.Have tests been written for this change?
No.
Have these commits been signed with GnuPG?
Yes.
Please review yadm's Contributing Guide for best practices.