|
From: | Uday S Reddy |
Subject: | Re: Locks on the Bzr repository |
Date: | Sat, 21 Aug 2010 15:56:50 +0100 |
User-agent: | Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2 |
On 8/21/2010 2:45 PM, Óscar Fuentes wrote:
Not really (for the workflow advertised by Stephen and Karl.)
"Stephen" is Stephen Turnbull? But he is arguing for unbound branches now.
At the time (and possibly still now) rebasing was not the soundest part of bzr. So the remaining workflows were "merge+push" and "pull". "merge+push" have the serious inconveniences described on my other post on this thread. So Stephen went for the remaining one: "pull", which is simulated with bound branches. When a developer does "merge+commit" on his local branch bound to upstream, it is the equivalent of `pull' on the remote branch.
Thank you very much. This makes perfect sense. If you don't trust rebase, and there are good reasons not to, then the current workflow is probably the best way of doing things. And, given the workflow, bound branches serve the purpose perfectly fine. I get it now.
Given the situation, moving to git would seem like a good idea, because its rebase is trustworthy and should improve matters enormously.
Cheers, Uday
[Prev in Thread] | Current Thread | [Next in Thread] |