Timeline for Nested git repositories without submodules?
Current License: CC BY-SA 2.5
Post Revisions
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 7, 2019 at 11:39 | answer | added | MatPag | timeline score: 0 | |
| Jul 13, 2016 at 5:04 | comment | added | Saeed Neamati | Are you sure that a git repo inside a parent repo isn't included in a commit on the parent unless it's setup as a submodule? Because that's what I want, and if you're right, then Git has that out-of-the-box. | |
| Nov 13, 2015 at 21:31 | answer | added | Drew LeSueur | timeline score: 9 | |
| Nov 26, 2013 at 22:21 | answer | added | funroll | timeline score: 0 | |
| Aug 25, 2011 at 20:09 | comment | added | user597474 | It sounds like what you really want is a subtree merge. That will leave you with a single repository and a single history. | |
| Jun 23, 2010 at 18:38 | answer | added | imz -- Ivan Zakharyaschev | timeline score: 2 | |
| Feb 23, 2010 at 12:24 | vote | accept | stevo | ||
| Feb 23, 2010 at 12:04 | comment | added | VonC | I am not sure if this is the right way to "mange dependencies", but I propose two ways to achieve what you want, plus some precisions about the nature of submodules in Git. | |
| Feb 23, 2010 at 11:59 | answer | added | VonC | timeline score: 9 | |
| Feb 23, 2010 at 11:27 | history | asked | stevo | CC BY-SA 2.5 |