Re: [git-users] What is the best technique to split the code between repos?

This might not be the *best* way to approach this, but what if you one repo with 3 unique branches: A, B, C; then two other branches, i.e.: AB, BC. You would then do work in the unique branches and pull changes from them into the combined ones when needed. Again, this might not be ideal, but

[git-users] Re: What is the best technique to split the code between repos?

Thanks, Joe. The idea is interesting but imagine then what repository would look like: At least 3 shared branches. Developing code always in branches and never come back to the master. On Sep 13, 5:43 pm, Joe Hassick ehass...@gmail.com wrote: This might not be the *best* way to approach this,