Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FAQ references "files.gpg" instead of "encrypt". #334

Open
ericvsmith opened this issue Apr 28, 2021 · 7 comments
Open

FAQ references "files.gpg" instead of "encrypt". #334

ericvsmith opened this issue Apr 28, 2021 · 7 comments
Labels

Comments

@ericvsmith
Copy link

It looks like this didn't get updated when the file name changed.

PR to follow.

@rasa
Copy link
Contributor

rasa commented May 1, 2021

@ericvsmith You are right that the file files.gpg was obsolete. Unfortunately, it was renamed to ~/.local/share/yadm/archive, not ~/.config/yadm/encrypt. That file is still used and contains the names of the files to be encrypted. I created #336 #337 to fix. I hope this is OK, as I don't want to step on your toes. If Tim rejects my PR and asks you to update yours, I will not take offense, Thanks for catching this!

@ericvsmith
Copy link
Author

I can't believe I screwed that up! Thanks for catching it. I'll close #335 in deference to #336.

@rasa
Copy link
Contributor

rasa commented May 1, 2021

No, thank YOU for catching the glitch! And thanks for not taking offense. I should have just commented on #334 and let you fix/close the PR as you saw fit.

@ericvsmith
Copy link
Author

We're all just trying to make yadm better. It's not possible to take offense on such constructive (and correct) criticism. I'd forgotten to sign #334, so now you've saved me the hassle!

@rasa
Copy link
Contributor

rasa commented May 1, 2021

@ericvsmith Yeah, but at least you branched off dev-pages! I screwed up #336 by branching off of gh-pages. Fixed in #337.

@github-actions
Copy link

This issue has been labeled as stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@github-actions
Copy link

This issue has been labeled as stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants