Push after commit --local

[James Henstridge]

On 19/09/06, Matthieu Moy <Matthieu.Moy at imag.fr> wrote:
> Hi,
>
> I'm looking for the best way to push locally commited revision to the
> master branch. If the local and master have diverged, "update; commit"
> does the right thing.
>
> However, I often have the case where I do a local commit on my laptop,
> and then come back online, on a branch on which I'm the only commiter.
> In this case, "update" introduces an artefact on my history, which I
> don't want.
>
> "push sftp://path.to/master" is what I want, but I'd like it to be
> easier to type.
>
> Maybe
>
> $ bzr push --master
>
> could be implemented?
>
> ("push" without argument doesn't do the right thing since the
> remembered location can be different from the master branch)

How about making "bzr update" do a push in the case where the local
checkout's revision history is a strict superset of the master
branch's history?  Currently "bzr update" will convert the local
commits into a pending merge in this case, but simply pushing the
changes would seem useful here.

James.