Comment 5 for bug 65286
Revision history for this message
| Vincent Ladeuil (vila) wrote Re: [Bug 65286] Re: bzr push should not work by default if there are uncommited changes | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
e3ace39
(Get the code!)
>>>>> "jam" == John A Meinel <email address hidden> writes:
jam> So I can certainly think of cases, like pushing up what
jam> I'm working on before I switch to commit my changes to a
jam> different branch.
Same here.
jam> I won't say it is the more common case, but it is a
jam> clear use case for having the ability to push when there
jam> are uncommitted changes.
I always thought so. Yet, for *new* users, that behavior will be
surprising (I know it has been for me, long ago).
So I understand the rationale for making it the default.
Yet, like you, I certainly want to be able to override it, that's
why I added configurations variables in addition to the
command-line option, as soon as I begun working on the bug.