background process for pushing my changes somewhere
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Low
|
Unassigned |
Bug Description
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.
description: | updated |
Changed in bzr: | |
importance: | Undecided → Low |
status: | New → Confirmed |
tags: | added: check-for-breezy |
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 :-)