Comment 4 for bug 539996
Revision history for this message
| Scott James Remnant (Canonical) (canonical-scott) wrote Re: [Bug 539996] Re: bzr push should default to parent branch if that's writable | #4 |
© 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:31 +0000, Robert Collins wrote:
> 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.
>
That very same argument could be used to declare "checkout" dangerous.
"explicit target" sounds like the kind of thing that most non-bzr
developers don't know anything about
> Can I ask, if you want to change that branch, why you aren't doing a
> 'bzr checkout' of it instead?
>
Because I don't necessarily want every commit to go untested - I want to
have the opportunity to work on the package, test, build and only push
before I actually upload.
Scott
--
Scott James Remnant
<email address hidden>