Dear Scott,
In message 49FB6647.8060303@freescale.com you wrote:
Wolfgang Denk wrote:
Please use the "next" branch as base for any new work. Note: Please keep in mind that it will be rebased against master every now and then without warning.
It is difficult to use as a base a branch that is itself being rebased.
Yes, I am aware of this problem.
Why not just merge unless there's something that absolutely cannot stay in the history?
I can do that. But it might happen that I decide to rebase, and I wanted you to warn in advance that this might happen.
Will you be pulling things into the next branch periodically (by request?), or is it just for things that aren't going into custodian next branches? When the next merge window opens, will next beecome master, or is it just an integration test as in linux-next?
I will pull into next if anybody sends me a pull request (and I appreciate if that happens as it reduces the amount of pending patches).
Before the merge window opens, I will merge next into master.
If integration tests are needed, we use u-boot-testing for this purpose.
Best regards,
Wolfgang Denk