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

borg info requires repo_or_archive param #1914

Closed
ThomasWaldmann opened this issue Dec 1, 2016 · 6 comments
Closed

borg info requires repo_or_archive param #1914

ThomasWaldmann opened this issue Dec 1, 2016 · 6 comments
Labels

Comments

@ThomasWaldmann
Copy link
Member

So, just setting BORG_REPO env var and doing a borg info (without the param) does not work.

See how borg list does it, it works there.

Found in master branch, check 1.0-maint also.

@david-azevedo
Copy link

hey i am entering the open-source community, can i take a look?

@ThomasWaldmann
Copy link
Member Author

sure, see archiver.py.

@david-azevedo
Copy link

on it, Thanks!

joaocsf added a commit to JoseLuisMartins/borg that referenced this issue Dec 2, 2016
@ThomasWaldmann
Copy link
Member Author

ThomasWaldmann commented Dec 2, 2016

@joaocsf if you end your commit comment with ", fixes #1914", github will automatically close #1914.

Fixed by #1917. Closing manually...

@enkore
Copy link
Contributor

enkore commented Dec 2, 2016

GitHub help: https://help.github.com/articles/closing-issues-via-commit-messages/

It also works in the opening comment of a pull request.

@joaocsf
Copy link
Contributor

joaocsf commented Dec 2, 2016

Sorry, I didn't knew about that. Thank you for the information! I'm learning alot with this project!

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

4 participants