You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: en/book/02-git-basics/chapter2.asc
+17-17Lines changed: 17 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,14 +37,14 @@ You clone a repository with `git clone [url]`. For example, if you want to clone
37
37
38
38
[source,shell]
39
39
----
40
-
$ git clone git://github.com/schacon/grit.git
40
+
$ git clone https://github.com/schacon/grit.git
41
41
----
42
42
43
43
That creates a directory named ``grit'', initializes a `.git` directory inside it, pulls down all the data for that repository, and checks out a working copy of the latest version. If you go into the new `grit` directory, you’ll see the project files in there, ready to be worked on or used. If you want to clone the repository into a directory named something other than grit, you can specify that as the next command-line option:
This means we can pull contributions from any of these users pretty easily. But notice that only the origin remote is an SSH URL, so it’s the only one I can push to (we’ll cover why this is in <<_git_on_the_server>>).
936
+
This means we can pull contributions from any of these users pretty easily. Notice that these remotes use a variety of protocols; we’ll cover why more about this in <<_git_on_the_server>>.
937
937
938
938
==== Adding Remote Repositories
939
939
@@ -943,12 +943,12 @@ I’ve mentioned and given some demonstrations of adding remote repositories in
Now you can use the string `pb` on the command line in lieu of the whole URL. For example, if you want to fetch all the information that Paul has but that you don’t yet have in your repository, you can run `git fetch pb`:
0 commit comments