Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to create two Git repositories in the same base directory, without using branches?
    primarykey
    data
    text
    <p>We are currently in the process of moving our Magento Enterprise (an e-commerce web application) files into Git. The httpdocs/.gitignore file contains, among other things:</p> <pre><code>app/design/frontend/company/website/ skin/frontend/company/website/ </code></pre> <p>After initializing, committing and pushing httpdocs/, our first Git repository was successfully created. We now want to put both of the aforementioned directories into their own, separate repository. (Together, in a single repository!) The problem we run into here is that these directories share a common root that already contains our first Git repository; that is: httpdocs/</p> <p>I've read it is possible with the submodule functionality to embed other repositories within subdirectories of existing trees. However, the documentation at for example <a href="https://git.wiki.kernel.org/index.php/GitSubmoduleTutorial" rel="nofollow">kernel.org</a> and <a href="http://book.git-scm.com/5_submodules.html" rel="nofollow">git-scm.com</a> seems so complicated that it makes me wonder whether this is really the way to go forward. All we need is two separate repositories, they just happen to have the same root.</p> <p>Another possible solution I've read about might be to initialize from app/design/frontend/company/website/ and add skin/frontend/company/website/ as a graft point in order to join these directories together. However, again, this seems overly complicated, and intended rather to be used when moving from another revision control system to Git.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload