Comment 3 for bug 539996
Revision history for this message
| Robert Collins (lifeless) wrote Re: [Bug 539996] Re: bzr push should default to parent branch if that's writable | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
On Wed, 2010-03-17 at 02:02 +0000, Scott James Remnant wrote:
>
> If they can write to the branch, why would it be unsafe? If they
> didn't
> mean to push there, they wouldn't have typed "push" unguarded
They might not know that bzr would push to that branch; they might have
thought they had set an explicit target and hadn't.
> - and they
> have permission to uncommit and push --overwrite as well.
Not if the branch is set to prevent uncommit and push --overwrite, which
many trunk branches are. Also after pushing some environments trigger
large tasks like CI test runs, so uncommitting isn't enough to undo
whatever they did.
> > As a workaround you should be able to do 'bzr push
> --remember :parent'.
> >
> Yes, but bzr is just being annoying ;)
>
> bzr papercut! :D
I can see that it is annoying you, that doesn't mean that its the wrong
behaviour.
Can I ask, if you want to change that branch, why you aren't doing a
'bzr checkout' of it instead?
-Rob