Removing branch= option will not default back to master

[iivvoo]

I occasionally need to checkout a specific branch, e.g.

[mr.developer]
foo = git [email protected]:example/foo.git branch=cutting-edge

Once the work on that branch has been merged into the master, I can depend on the master again, so:

[mr.developer]
foo = git [email protected]:example/foo.git

However, that will change nothing. I would expect mr.developer to switch to the master, but it doesn't. The only way is to force it using "branch=master"

Is there a specific reason for this behaviour? If not, can it default as expected?

[mauritsvanrees]

I am seeing this too when working on the Plone core-dev buildout. For example:

• bin/buildout -c plips/some-plip.cfg (this has branches of a few packages)
• bin/buildout (this should use master again, but it does not)

Workaround is probably indeed to say branch=master in the sources that are used in the default buildout.cfg.