--stdlayout在git svn clone中做了什么? [英] What does the --stdlayout do in git svn clone?
问题描述
我刚刚发现了这个问题,关于从克隆完成恢复没有--stdlayout。我没有找到这个标志的文档 - 它是做什么的?
Subversion没有任何分支或标记。相反,通常只需将存储库内容复制到一个目录即可模拟这些文件。
为了使 git svn
要能够识别分支和标签以及主分支(主干),必须使用 - 标签
(或 -t
), - 分支
(或 -b
)和 - 干线
(或 -T
)选项。
然而,许多Subversion版本库遵循Subversion书中列出的
- trunk = / trunk --branches = / branches --tags = / tags
。 - stdlayout
(或 -s
)对此约定进行编码,因此您不必传递相同的参数你可以在 git-svn(1)
手册中找到这些信息。页面,您可以在Unix下通过 man git-svn
以独立于操作系统的方式通过内置的Git帮助系统访问 git help svn
。 所有的Git手册页也可以在Kernel.Org上找到,它们是通常是您搜索 git-svn(1)$>时的第一个搜索结果c $ c>
。 I just spotted this question about recovering from a clone done without --stdlayout. I didn't find documentation of this flag - what does it do?
Subversion doesn't have any concept of branch or tag. Instead, those are typically simulated by simply copying the contents of the repository into a directory.
In order for git svn
to be able to recognize branches and tags and the main branch ("trunk"), you have to explicitly tell it where to find them, using the --tags
(or -t
), --branches
(or -b
) and --trunk
(or -T
) options.
However, many Subversion repositories follow a standard convention, laid out in the Subversion book, of --trunk=/trunk --branches=/branches --tags=/tags
. --stdlayout
(or -s
) encodes this convention, so that you don't have to pass the same arguments every time you clone a Subversion repository.
You can find this information in the git-svn(1)
manual page, which you can access under Unix with man git-svn
and in an operating system independent fashion via the builtin Git help system with git help svn
. All of the Git man pages are also available on Kernel.Org and they are usually the first search result when you search for git-svn(1)
.
这篇关于--stdlayout在git svn clone中做了什么?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!