background process for pushing my changes somewhere

[Glyph Lefkowitz]

I don't want to use bound branches, because sometimes I'm not online, and sometimes I'm on a slow network, where a bound branch means a substantially longer time waiting for 'bzr commit' to finish on the command line.

But, I also don't want to lose branches where I have hundreds of revisions on my laptop that I've forgotten to push anywhere useful.

Ideally, 'bzr commit' would always complete immediately, even for a bound branch, but a little icon in my menubar (or gnome panel, or systray) would show the progress of the push. More importantly, it would remember when I had unpushed changes that I'd committed while offline or on an impractically slow network, and resume pushing them later.

[Max Bowsher (maxb)]

It's not feasible for a commit to complete immediately for a bound branch, because a bound branch is defined to have successfully updated the remote branch before a commit succeeds.

For non-bound branches, though, a background push automatically after commit would certainly be interesting. It would, however, include the possibility of such a push failing. Still, that shouldn't happen too often, so the idea of 'bzr push' optionally backgrounding itself after write-locking the destination is certainly a very interesting one :-)

[Glyph Lefkowitz (glyph)]

Well, OK, call it whatever you want: partially bound, weakly bound, whatever - the important thing to me is the feature, not what it's called :).

I think that if the push fails, leaving the dead head revision in the remote branch would be sufficient (the changes are there and ready to be merged if anyone cares to dig them out).

[Robert Collins (lifeless)]

commit --local is intended to succeed immediately, with a push later
to sync (and if that cannot complete, update + commit to resolve).
This is a fair way towards what is asked for, I think.

[Glyph Lefkowitz (glyph)]

Robert: I do know about commit --local. What I'm looking for is really a way to have confidence that my changes are always eventually synced somewhere else, without having to block my workflow on slow networks or later remember that I manually need to push somewhere. The current situation is hardly *bad* - I can and do remember to push changes the vast majority of the time - but having something non-blocking in the background would be even better.

[Martin Pool (mbp)]

I think this would be a great feature.
--
Martin