bzr push should not work by default if there are uncommited changes

See also bug 206577 asking for this to be done for bzr send, and mysql bug 322808.

pqm-send apparently does this check already; it should be unified.

So I can certainly think of cases, like pushing up what I'm working on before I switch to commit my changes to a different branch. I won't say it is the more common case, but it is a clear use case for having the ability to push when there are uncommitted changes.

I should also mention that "pqm-submit" (IMO) is a much stronger action, as it is "merge this into the final product", which is has a different set of implications than "make this work public for someone else to get". Anyway, I'm very happy to have a flag for it, just pointing out places where it isn't exactly like what 'pqm-submit' does today.

>>>>> "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.