-
Notifications
You must be signed in to change notification settings - Fork 181
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
Add git clone to BUILD instructions #584
Comments
This sounds more like a development question rather than an issue with Dangerzone, so I'll reply on our github discussions forum instead and close this. Let's continue the conversation here #585 |
deeplow
changed the title
Poetry is installed and added to path but other issue
Add git clone to BUILD instructions
Oct 7, 2023
I have now added "git clone" instructions to the build instructions. Hopefully that makes it clearer. Thanks for bringing up the issue @mc-gitdeb. Closed by #594 |
Thank you too,
Good job, very prompt 👍
…________________________________
From: deeplow ***@***.***>
Sent: Thursday 19 October 2023 13:27
To: freedomofpress/dangerzone ***@***.***>
Cc: mc-gitdeb ***@***.***>; Mention ***@***.***>
Subject: Re: [freedomofpress/dangerzone] Add git clone to BUILD instructions (Issue #584)
I have now added "git clone" instructions to the build instructions. Hopefully that makes it clearer. Thanks for bringing up the issue @mc-gitdeb<https://github.com/mc-gitdeb>.
Closed by #594<#594>
—
Reply to this email directly, view it on GitHub<#584 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A5EGU52BIZFBEER2LUBKE73YAEMBJAVCNFSM6AAAAAA5XBFHNOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZQHA3DOMRTGY>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have poetry installed and added to my PATH but I can't seem to find my dangerzone folder,
Do I need to download something else first?
The text was updated successfully, but these errors were encountered: