On 4 Jun 2018, at 18:59, Tim Mackinnon <tim@testit.works> wrote:
P7 will force you to be in the right branch or you will not be able to do⦠almost anything :) you can have two (or ten) images opened at once and work on them, but at a moment you will need to ârepairâ each image to commit.
So are we saying that the easiest and less complicated option is to just have local copies for every project. These days, disk space is pretty cheap (and projects arenât that big source wise)?
is about you :)
Iâm sure for others it might be a bigger deal - but Iâm trying to understand what is the easiest option to avoid gotchaâs (that more advanced guys can better cope with)
most of the time you do not switch all the time. most of the time you can work on a feature in image A that will detach image B. But then, most of the time you will want to update image B (or kept it detached, is your choice). cheers, Esteban
Tim
On 4 Jun 2018, at 14:59, Esteban Lorenzano <estebanlm@gmail.com> wrote:
hi,
On 4 Jun 2018, at 12:57, Stephan Eggermont <stephan@stack.nl> wrote:
Evan Donahue <emdonahu@gmail.com> wrote:
I have "Share repositories between images" checked in both images,
Share repositories at the moment just provides a shared location on disk where the repositories are located. That is only useful if you are very disciplined about stashing and switching to the branch needed for your current image, and you only have one image open at a time.
not really. P7 will force you to be in the right branch or you will not be able to do⦠almost anything :) you can have two (or ten) images opened at once and work on them, but at a moment you will need to ârepairâ each image to commit.
Esteban
Stephan