© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I perceive this bug as a show stopper that is presently preventing me upgrading our team to the LTS 2.0 version.
Since the work flow we follow uses 'branch --stacked', the sticking plaster that has been applied now breaks this flow. Neither of the proposed workarounds are attractive as they both impose extra performance/disk overhead. BTW we have not experienced a single problem with this flow using bzr 1.7.
How do you think l my users would react if I upgrade the scripting to workaround this bug and released 2.0 with an announcement:
Upgrading to the new 2.0 version of bzr - which has as an added feature that commits will be about 3 -10 times slower AND use lots of extra disk space?
Like John S, I would like to see this bug fixed - at least assign it to somebody who can fix it. Presently the only thing most commentary here seems to care about is the exact wording of the bug title and the message the sticking plaster code produces. After all, if the bug was fixed nobody would give a damn what the message used to say.