| blob | 0207adda742fdb35327888d567658e8c870b196a |
1 '\" t
2 .\" Title: git-clone
3 .\" Author: [FIXME: author] [see http://www.docbook.org/tdg5/en/html/author]
4 .\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
5 .\" Date: 02/17/2022
6 .\" Manual: Git Manual
7 .\" Source: Git 2.35.1.225.ge2ac9141e6
8 .\" Language: English
9 .\"
10 .TH "GIT\-CLONE" "1" "02/17/2022" "Git 2\&.35\&.1\&.225\&.ge2ac91" "Git Manual"
11 .\" -----------------------------------------------------------------
12 .\" * Define some portability stuff
13 .\" -----------------------------------------------------------------
14 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
15 .\" http://bugs.debian.org/507673
16 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
17 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
18 .ie \n(.g .ds Aq \(aq
19 .el .ds Aq '
20 .\" -----------------------------------------------------------------
21 .\" * set default formatting
22 .\" -----------------------------------------------------------------
23 .\" disable hyphenation
24 .nh
25 .\" disable justification (adjust text to left margin only)
26 .ad l
27 .\" -----------------------------------------------------------------
28 .\" * MAIN CONTENT STARTS HERE *
29 .\" -----------------------------------------------------------------
30 .SH "NAME"
31 git-clone \- Clone a repository into a new directory
32 .SH "SYNOPSIS"
33 .sp
34 .nf
35 \fIgit clone\fR [\-\-template=<template\-directory>]
36 [\-l] [\-s] [\-\-no\-hardlinks] [\-q] [\-n] [\-\-bare] [\-\-mirror]
37 [\-o <name>] [\-b <name>] [\-u <upload\-pack>] [\-\-reference <repository>]
38 [\-\-dissociate] [\-\-separate\-git\-dir <git\-dir>]
39 [\-\-depth <depth>] [\-\-[no\-]single\-branch] [\-\-no\-tags]
40 [\-\-recurse\-submodules[=<pathspec>]] [\-\-[no\-]shallow\-submodules]
41 [\-\-[no\-]remote\-submodules] [\-\-jobs <n>] [\-\-sparse] [\-\-[no\-]reject\-shallow]
42 [\-\-filter=<filter>] [\-\-] <repository>
43 [<directory>]
44 .fi
45 .sp
46 .SH "DESCRIPTION"
47 .sp
48 Clones a repository into a newly created directory, creates remote\-tracking branches for each branch in the cloned repository (visible using \fBgit branch \-\-remotes\fR), and creates and checks out an initial branch that is forked from the cloned repository\(cqs currently active branch\&.
49 .sp
50 After the clone, a plain \fBgit fetch\fR without arguments will update all the remote\-tracking branches, and a \fBgit pull\fR without arguments will in addition merge the remote master branch into the current master branch, if any (this is untrue when "\-\-single\-branch" is given; see below)\&.
51 .sp
52 This default configuration is achieved by creating references to the remote branch heads under \fBrefs/remotes/origin\fR and by initializing \fBremote\&.origin\&.url\fR and \fBremote\&.origin\&.fetch\fR configuration variables\&.
53 .SH "OPTIONS"
54 .PP
55 \-l, \-\-local
56 .RS 4
57 When the repository to clone from is on a local machine, this flag bypasses the normal "Git aware" transport mechanism and clones the repository by making a copy of HEAD and everything under objects and refs directories\&. The files under
58 \fB\&.git/objects/\fR
59 directory are hardlinked to save space when possible\&.
60 .sp
61 If the repository is specified as a local path (e\&.g\&.,
62 \fB/path/to/repo\fR), this is the default, and \-\-local is essentially a no\-op\&. If the repository is specified as a URL, then this flag is ignored (and we never use the local optimizations)\&. Specifying
63 \fB\-\-no\-local\fR
64 will override the default when
65 \fB/path/to/repo\fR
66 is given, using the regular Git transport instead\&.
67 .sp
68 \fBNOTE\fR: this operation can race with concurrent modification to the source repository, similar to running
69 \fBcp \-r src dst\fR
70 while modifying
71 \fBsrc\fR\&.
72 .RE
73 .PP
74 \-\-no\-hardlinks
75 .RS 4
76 Force the cloning process from a repository on a local filesystem to copy the files under the
77 \fB\&.git/objects\fR
78 directory instead of using hardlinks\&. This may be desirable if you are trying to make a back\-up of your repository\&.
79 .RE
80 .PP
81 \-s, \-\-shared
82 .RS 4
83 When the repository to clone is on the local machine, instead of using hard links, automatically setup
84 \fB\&.git/objects/info/alternates\fR
85 to share the objects with the source repository\&. The resulting repository starts out without any object of its own\&.
86 .sp
87 \fBNOTE\fR: this is a possibly dangerous operation; do
88 \fBnot\fR
89 use it unless you understand what it does\&. If you clone your repository using this option and then delete branches (or use any other Git command that makes any existing commit unreferenced) in the source repository, some objects may become unreferenced (or dangling)\&. These objects may be removed by normal Git operations (such as
90 \fBgit commit\fR) which automatically call
91 \fBgit maintenance run \-\-auto\fR\&. (See
92 \fBgit-maintenance\fR(1)\&.) If these objects are removed and were referenced by the cloned repository, then the cloned repository will become corrupt\&.
93 .sp
94 Note that running
95 \fBgit repack\fR
96 without the
97 \fB\-\-local\fR
98 option in a repository cloned with
99 \fB\-\-shared\fR
100 will copy objects from the source repository into a pack in the cloned repository, removing the disk space savings of
101 \fBclone \-\-shared\fR\&. It is safe, however, to run
102 \fBgit gc\fR, which uses the
103 \fB\-\-local\fR
104 option by default\&.
105 .sp
106 If you want to break the dependency of a repository cloned with
107 \fB\-\-shared\fR
108 on its source repository, you can simply run
109 \fBgit repack \-a\fR
110 to copy all objects from the source repository into a pack in the cloned repository\&.
111 .RE
112 .PP
113 \-\-reference[\-if\-able] <repository>
114 .RS 4
115 If the reference repository is on the local machine, automatically setup
116 \fB\&.git/objects/info/alternates\fR
117 to obtain objects from the reference repository\&. Using an already existing repository as an alternate will require fewer objects to be copied from the repository being cloned, reducing network and local storage costs\&. When using the
118 \fB\-\-reference\-if\-able\fR, a non existing directory is skipped with a warning instead of aborting the clone\&.
119 .sp
120 \fBNOTE\fR: see the NOTE for the
121 \fB\-\-shared\fR
122 option, and also the
123 \fB\-\-dissociate\fR
124 option\&.
125 .RE
126 .PP
127 \-\-dissociate
128 .RS 4
129 Borrow the objects from reference repositories specified with the
130 \fB\-\-reference\fR
131 options only to reduce network transfer, and stop borrowing from them after a clone is made by making necessary local copies of borrowed objects\&. This option can also be used when cloning locally from a repository that already borrows objects from another repository\(emthe new repository will borrow objects from the same repository, and this option can be used to stop the borrowing\&.
132 .RE
133 .PP
134 \-q, \-\-quiet
135 .RS 4
136 Operate quietly\&. Progress is not reported to the standard error stream\&.
137 .RE
138 .PP
139 \-v, \-\-verbose
140 .RS 4
141 Run verbosely\&. Does not affect the reporting of progress status to the standard error stream\&.
142 .RE
143 .PP
144 \-\-progress
145 .RS 4
146 Progress status is reported on the standard error stream by default when it is attached to a terminal, unless
147 \fB\-\-quiet\fR
148 is specified\&. This flag forces progress status even if the standard error stream is not directed to a terminal\&.
149 .RE
150 .PP
151 \-\-server\-option=<option>
152 .RS 4
153 Transmit the given string to the server when communicating using protocol version 2\&. The given string must not contain a NUL or LF character\&. The server\(cqs handling of server options, including unknown ones, is server\-specific\&. When multiple
154 \fB\-\-server\-option=<option>\fR
155 are given, they are all sent to the other side in the order listed on the command line\&.
156 .RE
157 .PP
158 \-n, \-\-no\-checkout
159 .RS 4
160 No checkout of HEAD is performed after the clone is complete\&.
161 .RE
162 .PP
163 \-\-[no\-]reject\-shallow
164 .RS 4
165 Fail if the source repository is a shallow repository\&. The
166 \fIclone\&.rejectShallow\fR
167 configuration variable can be used to specify the default\&.
168 .RE
169 .PP
170 \-\-bare
171 .RS 4
172 Make a
173 \fIbare\fR
174 Git repository\&. That is, instead of creating
175 \fB<directory>\fR
176 and placing the administrative files in
177 \fB<directory>/\&.git\fR, make the
178 \fB<directory>\fR
179 itself the
180 \fB$GIT_DIR\fR\&. This obviously implies the
181 \fB\-\-no\-checkout\fR
182 because there is nowhere to check out the working tree\&. Also the branch heads at the remote are copied directly to corresponding local branch heads, without mapping them to
183 \fBrefs/remotes/origin/\fR\&. When this option is used, neither remote\-tracking branches nor the related configuration variables are created\&.
184 .RE
185 .PP
186 \-\-sparse
187 .RS 4
188 Employ a sparse\-checkout, with only files in the toplevel directory initially being present\&. The
189 \fBgit-sparse-checkout\fR(1)
190 command can be used to grow the working directory as needed\&.
191 .RE
192 .PP
193 \-\-filter=<filter\-spec>
194 .RS 4
195 Use the partial clone feature and request that the server sends a subset of reachable objects according to a given object filter\&. When using
196 \fB\-\-filter\fR, the supplied
197 \fB<filter\-spec>\fR
198 is used for the partial clone filter\&. For example,
199 \fB\-\-filter=blob:none\fR
200 will filter out all blobs (file contents) until needed by Git\&. Also,
201 \fB\-\-filter=blob:limit=<size>\fR
202 will filter out all blobs of size at least
203 \fB<size>\fR\&. For more details on filter specifications, see the
204 \fB\-\-filter\fR
205 option in
206 \fBgit-rev-list\fR(1)\&.
207 .RE
208 .PP
209 \-\-mirror
210 .RS 4
211 Set up a mirror of the source repository\&. This implies
212 \fB\-\-bare\fR\&. Compared to
213 \fB\-\-bare\fR,
214 \fB\-\-mirror\fR
215 not only maps local branches of the source to local branches of the target, it maps all refs (including remote\-tracking branches, notes etc\&.) and sets up a refspec configuration such that all these refs are overwritten by a
216 \fBgit remote update\fR
217 in the target repository\&.
218 .RE
219 .PP
220 \-o <name>, \-\-origin <name>
221 .RS 4
222 Instead of using the remote name
223 \fBorigin\fR
224 to keep track of the upstream repository, use
225 \fB<name>\fR\&. Overrides
226 \fBclone\&.defaultRemoteName\fR
227 from the config\&.
228 .RE
229 .PP
230 \-b <name>, \-\-branch <name>
231 .RS 4
232 Instead of pointing the newly created HEAD to the branch pointed to by the cloned repository\(cqs HEAD, point to
233 \fB<name>\fR
234 branch instead\&. In a non\-bare repository, this is the branch that will be checked out\&.
235 \fB\-\-branch\fR
236 can also take tags and detaches the HEAD at that commit in the resulting repository\&.
237 .RE
238 .PP
239 \-u <upload\-pack>, \-\-upload\-pack <upload\-pack>
240 .RS 4
241 When given, and the repository to clone from is accessed via ssh, this specifies a non\-default path for the command run on the other end\&.
242 .RE
243 .PP
244 \-\-template=<template\-directory>
245 .RS 4
246 Specify the directory from which templates will be used; (See the "TEMPLATE DIRECTORY" section of
247 \fBgit-init\fR(1)\&.)
248 .RE
249 .PP
250 \-c <key>=<value>, \-\-config <key>=<value>
251 .RS 4
252 Set a configuration variable in the newly\-created repository; this takes effect immediately after the repository is initialized, but before the remote history is fetched or any files checked out\&. The key is in the same format as expected by
253 \fBgit-config\fR(1)
254 (e\&.g\&.,
255 \fBcore\&.eol=true\fR)\&. If multiple values are given for the same key, each value will be written to the config file\&. This makes it safe, for example, to add additional fetch refspecs to the origin remote\&.
256 .sp
257 Due to limitations of the current implementation, some configuration variables do not take effect until after the initial fetch and checkout\&. Configuration variables known to not take effect are:
258 \fBremote\&.<name>\&.mirror\fR
259 and
260 \fBremote\&.<name>\&.tagOpt\fR\&. Use the corresponding
261 \fB\-\-mirror\fR
262 and
263 \fB\-\-no\-tags\fR
264 options instead\&.
265 .RE
266 .PP
267 \-\-depth <depth>
268 .RS 4
269 Create a
270 \fIshallow\fR
271 clone with a history truncated to the specified number of commits\&. Implies
272 \fB\-\-single\-branch\fR
273 unless
274 \fB\-\-no\-single\-branch\fR
275 is given to fetch the histories near the tips of all branches\&. If you want to clone submodules shallowly, also pass
276 \fB\-\-shallow\-submodules\fR\&.
277 .RE
278 .PP
279 \-\-shallow\-since=<date>
280 .RS 4
281 Create a shallow clone with a history after the specified time\&.
282 .RE
283 .PP
284 \-\-shallow\-exclude=<revision>
285 .RS 4
286 Create a shallow clone with a history, excluding commits reachable from a specified remote branch or tag\&. This option can be specified multiple times\&.
287 .RE
288 .PP
289 \-\-[no\-]single\-branch
290 .RS 4
291 Clone only the history leading to the tip of a single branch, either specified by the
292 \fB\-\-branch\fR
293 option or the primary branch remote\(cqs
294 \fBHEAD\fR
295 points at\&. Further fetches into the resulting repository will only update the remote\-tracking branch for the branch this option was used for the initial cloning\&. If the HEAD at the remote did not point at any branch when
296 \fB\-\-single\-branch\fR
297 clone was made, no remote\-tracking branch is created\&.
298 .RE
299 .PP
300 \-\-no\-tags
301 .RS 4
302 Don\(cqt clone any tags, and set
303 \fBremote\&.<remote>\&.tagOpt=\-\-no\-tags\fR
304 in the config, ensuring that future
305 \fBgit pull\fR
306 and
307 \fBgit fetch\fR
308 operations won\(cqt follow any tags\&. Subsequent explicit tag fetches will still work, (see
309 \fBgit-fetch\fR(1))\&.
310 .sp
311 Can be used in conjunction with
312 \fB\-\-single\-branch\fR
313 to clone and maintain a branch with no references other than a single cloned branch\&. This is useful e\&.g\&. to maintain minimal clones of the default branch of some repository for search indexing\&.
314 .RE
315 .PP
316 \-\-recurse\-submodules[=<pathspec>]
317 .RS 4
318 After the clone is created, initialize and clone submodules within based on the provided pathspec\&. If no pathspec is provided, all submodules are initialized and cloned\&. This option can be given multiple times for pathspecs consisting of multiple entries\&. The resulting clone has
319 \fBsubmodule\&.active\fR
320 set to the provided pathspec, or "\&." (meaning all submodules) if no pathspec is provided\&.
321 .sp
322 Submodules are initialized and cloned using their default settings\&. This is equivalent to running
323 \fBgit submodule update \-\-init \-\-recursive <pathspec>\fR
324 immediately after the clone is finished\&. This option is ignored if the cloned repository does not have a worktree/checkout (i\&.e\&. if any of
325 \fB\-\-no\-checkout\fR/\fB\-n\fR,
326 \fB\-\-bare\fR, or
327 \fB\-\-mirror\fR
328 is given)
329 .RE
330 .PP
331 \-\-[no\-]shallow\-submodules
332 .RS 4
333 All submodules which are cloned will be shallow with a depth of 1\&.
334 .RE
335 .PP
336 \-\-[no\-]remote\-submodules
337 .RS 4
338 All submodules which are cloned will use the status of the submodule\(cqs remote\-tracking branch to update the submodule, rather than the superproject\(cqs recorded SHA\-1\&. Equivalent to passing
339 \fB\-\-remote\fR
340 to
341 \fBgit submodule update\fR\&.
342 .RE
343 .PP
344 \-\-separate\-git\-dir=<git\-dir>
345 .RS 4
346 Instead of placing the cloned repository where it is supposed to be, place the cloned repository at the specified directory, then make a filesystem\-agnostic Git symbolic link to there\&. The result is Git repository can be separated from working tree\&.
347 .RE
348 .PP
349 \-j <n>, \-\-jobs <n>
350 .RS 4
351 The number of submodules fetched at the same time\&. Defaults to the
352 \fBsubmodule\&.fetchJobs\fR
353 option\&.
354 .RE
355 .PP
356 <repository>
357 .RS 4
358 The (possibly remote) repository to clone from\&. See the
359 GIT URLS
360 section below for more information on specifying repositories\&.
361 .RE
362 .PP
363 <directory>
364 .RS 4
365 The name of a new directory to clone into\&. The "humanish" part of the source repository is used if no directory is explicitly given (\fBrepo\fR
366 for
367 \fB/path/to/repo\&.git\fR
368 and
369 \fBfoo\fR
370 for
371 \fBhost\&.xz:foo/\&.git\fR)\&. Cloning into an existing directory is only allowed if the directory is empty\&.
372 .RE
373 .SH "GIT URLS"
374 .sp
375 In general, URLs contain information about the transport protocol, the address of the remote server, and the path to the repository\&. Depending on the transport protocol, some of this information may be absent\&.
376 .sp
377 Git supports ssh, git, http, and https protocols (in addition, ftp, and ftps can be used for fetching, but this is inefficient and deprecated; do not use it)\&.
378 .sp
379 The native transport (i\&.e\&. git:// URL) does no authentication and should be used with caution on unsecured networks\&.
380 .sp
381 The following syntaxes may be used with them:
382 .sp
383 .RS 4
384 .ie n \{\
385 \h'-04'\(bu\h'+03'\c
386 .\}
387 .el \{\
388 .sp -1
389 .IP \(bu 2.3
390 .\}
391 ssh://[user@]host\&.xz[:port]/path/to/repo\&.git/
392 .RE
393 .sp
394 .RS 4
395 .ie n \{\
396 \h'-04'\(bu\h'+03'\c
397 .\}
398 .el \{\
399 .sp -1
400 .IP \(bu 2.3
401 .\}
402 git://host\&.xz[:port]/path/to/repo\&.git/
403 .RE
404 .sp
405 .RS 4
406 .ie n \{\
407 \h'-04'\(bu\h'+03'\c
408 .\}
409 .el \{\
410 .sp -1
411 .IP \(bu 2.3
412 .\}
413 http[s]://host\&.xz[:port]/path/to/repo\&.git/
414 .RE
415 .sp
416 .RS 4
417 .ie n \{\
418 \h'-04'\(bu\h'+03'\c
419 .\}
420 .el \{\
421 .sp -1
422 .IP \(bu 2.3
423 .\}
424 ftp[s]://host\&.xz[:port]/path/to/repo\&.git/
425 .RE
426 .sp
427 An alternative scp\-like syntax may also be used with the ssh protocol:
428 .sp
429 .RS 4
430 .ie n \{\
431 \h'-04'\(bu\h'+03'\c
432 .\}
433 .el \{\
434 .sp -1
435 .IP \(bu 2.3
436 .\}
437 [user@]host\&.xz:path/to/repo\&.git/
438 .RE
439 .sp
440 This syntax is only recognized if there are no slashes before the first colon\&. This helps differentiate a local path that contains a colon\&. For example the local path \fBfoo:bar\fR could be specified as an absolute path or \fB\&./foo:bar\fR to avoid being misinterpreted as an ssh url\&.
441 .sp
442 The ssh and git protocols additionally support ~username expansion:
443 .sp
444 .RS 4
445 .ie n \{\
446 \h'-04'\(bu\h'+03'\c
447 .\}
448 .el \{\
449 .sp -1
450 .IP \(bu 2.3
451 .\}
452 ssh://[user@]host\&.xz[:port]/~[user]/path/to/repo\&.git/
453 .RE
454 .sp
455 .RS 4
456 .ie n \{\
457 \h'-04'\(bu\h'+03'\c
458 .\}
459 .el \{\
460 .sp -1
461 .IP \(bu 2.3
462 .\}
463 git://host\&.xz[:port]/~[user]/path/to/repo\&.git/
464 .RE
465 .sp
466 .RS 4
467 .ie n \{\
468 \h'-04'\(bu\h'+03'\c
469 .\}
470 .el \{\
471 .sp -1
472 .IP \(bu 2.3
473 .\}
474 [user@]host\&.xz:/~[user]/path/to/repo\&.git/
475 .RE
476 .sp
477 For local repositories, also supported by Git natively, the following syntaxes may be used:
478 .sp
479 .RS 4
480 .ie n \{\
481 \h'-04'\(bu\h'+03'\c
482 .\}
483 .el \{\
484 .sp -1
485 .IP \(bu 2.3
486 .\}
487 /path/to/repo\&.git/
488 .RE
489 .sp
490 .RS 4
491 .ie n \{\
492 \h'-04'\(bu\h'+03'\c
493 .\}
494 .el \{\
495 .sp -1
496 .IP \(bu 2.3
497 .\}
498 file:///path/to/repo\&.git/
499 .RE
500 .sp
501 These two syntaxes are mostly equivalent, except the former implies \-\-local option\&.
502 .sp
503 \fIgit clone\fR, \fIgit fetch\fR and \fIgit pull\fR, but not \fIgit push\fR, will also accept a suitable bundle file\&. See \fBgit-bundle\fR(1)\&.
504 .sp
505 When Git doesn\(cqt know how to handle a certain transport protocol, it attempts to use the \fIremote\-<transport>\fR remote helper, if one exists\&. To explicitly request a remote helper, the following syntax may be used:
506 .sp
507 .RS 4
508 .ie n \{\
509 \h'-04'\(bu\h'+03'\c
510 .\}
511 .el \{\
512 .sp -1
513 .IP \(bu 2.3
514 .\}
515 <transport>::<address>
516 .RE
517 .sp
518 where <address> may be a path, a server and path, or an arbitrary URL\-like string recognized by the specific remote helper being invoked\&. See \fBgitremote-helpers\fR(7) for details\&.
519 .sp
520 If there are a large number of similarly\-named remote repositories and you want to use a different format for them (such that the URLs you use will be rewritten into URLs that work), you can create a configuration section of the form:
521 .sp
522 .if n \{\
523 .RS 4
524 .\}
525 .nf
526 [url "<actual url base>"]
527 insteadOf = <other url base>
528 .fi
529 .if n \{\
530 .RE
531 .\}
532 .sp
533 .sp
534 For example, with this:
535 .sp
536 .if n \{\
537 .RS 4
538 .\}
539 .nf
540 [url "git://git\&.host\&.xz/"]
541 insteadOf = host\&.xz:/path/to/
542 insteadOf = work:
543 .fi
544 .if n \{\
545 .RE
546 .\}
547 .sp
548 .sp
549 a URL like "work:repo\&.git" or like "host\&.xz:/path/to/repo\&.git" will be rewritten in any context that takes a URL to be "git://git\&.host\&.xz/repo\&.git"\&.
550 .sp
551 If you want to rewrite URLs for push only, you can create a configuration section of the form:
552 .sp
553 .if n \{\
554 .RS 4
555 .\}
556 .nf
557 [url "<actual url base>"]
558 pushInsteadOf = <other url base>
559 .fi
560 .if n \{\
561 .RE
562 .\}
563 .sp
564 .sp
565 For example, with this:
566 .sp
567 .if n \{\
568 .RS 4
569 .\}
570 .nf
571 [url "ssh://example\&.org/"]
572 pushInsteadOf = git://example\&.org/
573 .fi
574 .if n \{\
575 .RE
576 .\}
577 .sp
578 .sp
579 a URL like "git://example\&.org/path/to/repo\&.git" will be rewritten to "ssh://example\&.org/path/to/repo\&.git" for pushes, but pulls will still use the original URL\&.
580 .SH "EXAMPLES"
581 .sp
582 .RS 4
583 .ie n \{\
584 \h'-04'\(bu\h'+03'\c
585 .\}
586 .el \{\
587 .sp -1
588 .IP \(bu 2.3
589 .\}
590 Clone from upstream:
591 .sp
592 .if n \{\
593 .RS 4
594 .\}
595 .nf
596 $ git clone git://git\&.kernel\&.org/pub/scm/\&.\&.\&./linux\&.git my\-linux
597 $ cd my\-linux
598 $ make
599 .fi
600 .if n \{\
601 .RE
602 .\}
603 .sp
604 .RE
605 .sp
606 .RS 4
607 .ie n \{\
608 \h'-04'\(bu\h'+03'\c
609 .\}
610 .el \{\
611 .sp -1
612 .IP \(bu 2.3
613 .\}
614 Make a local clone that borrows from the current directory, without checking things out:
615 .sp
616 .if n \{\
617 .RS 4
618 .\}
619 .nf
620 $ git clone \-l \-s \-n \&. \&.\&./copy
621 $ cd \&.\&./copy
622 $ git show\-branch
623 .fi
624 .if n \{\
625 .RE
626 .\}
627 .sp
628 .RE
629 .sp
630 .RS 4
631 .ie n \{\
632 \h'-04'\(bu\h'+03'\c
633 .\}
634 .el \{\
635 .sp -1
636 .IP \(bu 2.3
637 .\}
638 Clone from upstream while borrowing from an existing local directory:
639 .sp
640 .if n \{\
641 .RS 4
642 .\}
643 .nf
644 $ git clone \-\-reference /git/linux\&.git \e
645 git://git\&.kernel\&.org/pub/scm/\&.\&.\&./linux\&.git \e
646 my\-linux
647 $ cd my\-linux
648 .fi
649 .if n \{\
650 .RE
651 .\}
652 .sp
653 .RE
654 .sp
655 .RS 4
656 .ie n \{\
657 \h'-04'\(bu\h'+03'\c
658 .\}
659 .el \{\
660 .sp -1
661 .IP \(bu 2.3
662 .\}
663 Create a bare repository to publish your changes to the public:
664 .sp
665 .if n \{\
666 .RS 4
667 .\}
668 .nf
669 $ git clone \-\-bare \-l /home/proj/\&.git /pub/scm/proj\&.git
670 .fi
671 .if n \{\
672 .RE
673 .\}
674 .sp
675 .RE
676 .SH "GIT"
677 .sp
678 Part of the \fBgit\fR(1) suite