[MERGE] configuration policies
james at jamesh.id.au
Thu Dec 7 15:57:03 GMT 2006
On 27/11/06, James Henstridge <james at jamesh.id.au> wrote:
> On 26/11/06, Wouter van Heyst <larstiq at larstiq.dyndns.org> wrote:
> > Has anyone tried using this? If there are no quirky corners I think this
> > change would be very good to have.
> I've used it locally, and it seems to work okay :)
> It would be quite useful for Launchpad development since it means we
> generally work with short lived feature branches and it would allow
> developers to configure their "bzr push" and PQM submit locations once
> and have it work for all their branches.
> As far as nested trees go, this patch does change the behaviour a bit,
> but I consider the previous behaviour broken. Consider the following
> 1. user creates a branch as /a
> 2. user creates a nested branch as /a/b
> 3. user runs "bzr push http://myserver/a" when in /a
> This causes a push location to be remembered for /a. With current
> Bazaar, the remembered push location will also affect /a/b, so that
> "bzr push" in that branch will also push to http://myserver/a (not
> http://myserver/a/b). This is almost certainly not desired behaviour,
> since we have two different branches pushing to the same location.
> With my patch, the remembered push location for /a has the norecurse
> policy, so does not affect /a/b. This seemed to be the most
> conservative choice at this point.
Attached is an updated version of the config policies patch. The only
difference to the previous one is that I've updated the deprecation
message to note that the feature was introduced in bzr-0.14 rather
Previous versions of this patch have received +1's from Aaron and John.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 77303 bytes
Desc: not available
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20061208/30f1abe0/attachment.bin
More information about the bazaar