Use https instead of git@ for cloning instructions #29
Conversation
|
This should really be two different requests. You've also included a URL change for Ninja |
|
Excellent suggestion! I've updated my own PR #31 to include this change |
|
+1 |
|
why not |
|
+1 |
|
What about users who prefer SSH connections so that they don't have to enter a username and password every time they clone something? |
|
@vocaro This is a public repository so you wouldn't need to enter a username or password. |
|
+1 (:+1:) |
|
+1 |
|
I think you can configure your git settings to override it for you via insteadOf. |
|
This is really pointless. People should just create a GitHub account and SSH key. It takes less than 2 minutes to do so. |
|
@KamranMackey Swift, a project on Github, should follow Github's recommendations for method of cloning not user / your preference. https://help.github.com/articles/which-remote-url-should-i-use/#cloning-with-https-recommended |
|
This is now resolved by 15428fb. |
Initialise dispatch_queue_attr_concurrent on Linux
Initialise dispatch_queue_attr_concurrent on Linux Signed-off-by: Daniel A. Steffen <dsteffen@apple.com>
Fix the License for Fedora spec file
Cloning with
git@uses SSH and thus requires the user to have an account on GitHub and have an SSH key locally configured and attached to their GitHub account.Changing this to https removes these dependencies for users following instructions on the README.
This also updates links to ninja build repository and their new website.