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?
I just spotted this question about recovering from a clone done without –stdlayout. I
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
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 svnto 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 withman git-svnand in an operating system independent fashion via the builtin Git help system withgit 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 forgit-svn(1).