Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
李少辉-开发者
git
提交
b26f39cd
G
git
项目概览
李少辉-开发者
/
git
与 Fork 源项目一致
从无法访问的项目Fork
通知
2
Star
1
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
G
git
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
b26f39cd
编写于
11月 01, 2009
作者:
J
Junio C Hamano
浏览文件
操作
浏览文件
下载
差异文件
Merge branch 'bg/clone-doc' into maint
* bg/clone-doc: git-clone.txt: Fix grammar and formatting
上级
75457126
550c66f3
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
13 addition
and
13 deletion
+13
-13
Documentation/git-clone.txt
Documentation/git-clone.txt
+13
-13
未找到文件。
Documentation/git-clone.txt
浏览文件 @
b26f39cd
...
...
@@ -39,7 +39,7 @@ OPTIONS
--local::
-l::
When the repository to clone from is on a local machine,
this flag bypasses normal "git aware" transport
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 `.git/objects/` directory are hardlinked
...
...
@@ -60,7 +60,7 @@ OPTIONS
-s::
When the repository to clone is on the local machine,
instead of using hard links, automatically setup
.git/objects/info/alternates
to share the objects
`.git/objects/info/alternates`
to share the objects
with the source repository. The resulting repository
starts out without any object of its own.
+
...
...
@@ -69,7 +69,7 @@ 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
'git-commit'
)
These objects may be removed by normal git operations (such as
`git commit`
)
which automatically call `git gc --auto`. (See linkgit:git-gc[1].)
If these objects are removed and were referenced by the cloned repository,
then the cloned repository will become corrupt.
...
...
@@ -86,13 +86,13 @@ objects from the source repository into a pack in the cloned repository.
--reference <repository>::
If the reference repository is on the local machine,
automatically setup
.git/objects/info/alternates
to
automatically setup
`.git/objects/info/alternates`
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.
+
*NOTE*: see
NOTE to --shared
option.
*NOTE*: see
the NOTE for the `--shared`
option.
--quiet::
-q::
...
...
@@ -101,7 +101,7 @@ objects from the source repository into a pack in the cloned repository.
--verbose::
-v::
Display the progressbar, even in case the standard output is not
Display the progress
bar, even in case the standard output is not
a terminal.
--no-checkout::
...
...
@@ -121,17 +121,17 @@ objects from the source repository into a pack in the cloned repository.
configuration variables are created.
--mirror::
Set up a mirror of the remote repository. This implies
--bare
.
Set up a mirror of the remote repository. This implies
`--bare`
.
--origin <name>::
-o <name>::
Instead of using the remote name
'origin'
to keep track
of the upstream repository, use
<name>
.
Instead of using the remote name
`origin`
to keep track
of the upstream repository, use
`<name>`
.
--branch <name>::
-b <name>::
Instead of pointing the newly created HEAD to the branch pointed
to by the cloned repository's HEAD, point to
<name>
branch
to by the cloned repository's HEAD, point to
`<name>`
branch
instead. In a non-bare repository, this is the branch that will
be checked out.
...
...
@@ -158,7 +158,7 @@ objects from the source repository into a pack in the cloned repository.
--recursive::
After the clone is created, initialize all submodules within,
using their default settings. This is equivalent to running
'git submodule update --init --recursive'
immediately after
`git submodule update --init --recursive`
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
`--no-checkout`/`-n`, `--bare`, or `--mirror` is given)
...
...
@@ -171,8 +171,8 @@ objects from the source repository into a pack in the cloned repository.
<directory>::
The name of a new directory to clone into. The "humanish"
part of the source repository is used if no directory is
explicitly given (
"repo" for "/path/to/repo.git" and "foo"
for
"host.xz:foo/.git"
). Cloning into an existing directory
explicitly given (
`repo` for `/path/to/repo.git` and `foo`
for
`host.xz:foo/.git`
). Cloning into an existing directory
is only allowed if the directory is empty.
:git-clone: 1
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录