If you are familiar with symlinks under Linux, you can think of submodules
as such. You add a reference to another git repository, check it out to a
subdirectory, and you are done. The Git book has a chapter on it:
On 27 February 2013 23:21, Ben McCann <benjamin.j.mcc...@gmail.com> wrote:
> Anyone have any experience using subtree?
> On Monday, February 25, 2013 8:21:50 PM UTC-8, Ben McCann wrote:
>> I'm fairly new to git and am trying to determine if git subtree would be
>> helpful for managing our company's codebase, which has several repos some
>> of which depend on each other. All the examples I've seen make sense to me
>> as a one-time operation to merge separate repos into one monolithic one or
>> to split one monolithic repo into separate repos. I'm having a harder time
>> understanding how this fits into a larger picture and what the workflow for
>> working with subtree would be.
>> If I have a bunch of repos on GitHub and some depend on each other, how
>> would I set them up to work with subtree? Would GitHub continue to host
>> them as is, host a merged monolithic repo, or host both a monolithic repo
>> and the splitted out repo? The exact answer probably varies, but I imagine
>> there's basic workflow that would satisfy 80% of users. If I have GitHub
>> host both monolithic and splitted out repos, it seems unclear as to how I
>> keep those repos in sync and make sure all the developers in our company
>> push their changes to both repos.
> You received this message because you are subscribed to the Google Groups
> "Git for human beings" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to git-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/groups/opt_out.