Databases
StackOverflow2013
Postsdbo
POGit. Store several projects under the same repository
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGit. Store several projects under the same repository
    primarykey
    data
    text
    <p>Imagine mobile application that is planned to be implemented for both iOS and Android. Development was started from the iOS version only and now the time has come to start with Android one. iOS application's code is stored at its' own Git repository that named after the apps name, e.g. "MYApp". Now I would like to create one common repository for both iOS and Android applications and name it again after application's name: "MYApp".</p> <p>It is not a problem at first glance. Just create repository, create 2 subfolders there and start working.</p> <p>But. I would like that Android developer could work only with his folder and iOS developer only with his one too and both of them could see only their own folders related history (log).</p> <p>I worked with SVN previously. Usually I created subfolders and you could checkout any of them to work only with this subfolder. History was also filtered to your scope.</p> <p>I'm stuck with implementing the same under Git. Please, help me to find right direction.</p> <hr> <p><strong>I will sum up solutions suggested.</strong></p> <ol> <li>Use branching for different platforms. I don't think that it is good idea, because branches used for another purpose. It seems to me very "jacky".</li> <li>Use submodules. Just create as many repos as platforms you are targeting to, name them "MYApp-iOS", "MyApp-Android", etc. and finally end up with "master" repo, that could be names as "MYApp" (without any suffixes). Then add all related repos to "master" one with git submodules feature.</li> <li>Use git slave. Investigating...</li> </ol> <p>Please, feel free to edit this list to brainstorm the problem.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDaddyM
    1. USDaddyM
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POGit. Store several projects under the same repository
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POGit. Store several projects under the same repository
      1. USRok Jarc
      1. VTFavorite
    1. COYou could try with two [branches](http://git-scm.com/book/en/Git-Branching) but this really doesn't sound like a good idea. Do you have a really really good reason not to use two separate repositories?
      singulars
      1. POGit. Store several projects under the same repository
      1. USRok Jarc
    2. COA question that is kind of related to your problem: http://stackoverflow.com/q/466303/653513
      singulars
      1. POGit. Store several projects under the same repository
      1. USRok Jarc
    3. COWouldn't this be a nice case for using submodules? Just have the two repos and use submodules for the main repo with both projects in them
      singulars
      1. POGit. Store several projects under the same repository
      1. USHugo Tunius
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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