Public bug reported:
Binary package hint: bzr
It would be nice to improve usability of bzr between 2 computers or more
to synchronize uncommitted code. This has been discussed on IRC when I
first bring the topic there.
Use case:
1/ Max works from home (computer A) or from the office (computer B)
2/ Max is working on a project where the workflow is to commit to the
central/shared branch (on computer C) only complete patches (the tree must
always build)
3/ The patch Max is working on is taking several days so he cannot commit to C
to pass code between A and B (because it's not complete). Fake commit/uncommits
are also unacceptable because the branch is shared and it will force A or B to
push in override mode which could easily lead to loss of data.
4/ shared filesystems between A and B are not an option, and transport has to
be on ssh, preferably doable from the side only (the other side could be
firewalled, NATed or simply use a dynamic IP)
It is possible to scp the whole tree from A to B, then diff the two working
trees and patch B but it's laborious.
Another option would be to revert B and pass a bzr diff from A to B, but it
could lead to loss of data on B if B had diverged (a merge would have prevented
that).
A better proposal on IRC was to use merge --uncommitted but it doesn't
currently work on bzr+ssh or sftp ("is not a local path").
a bzr sync would be nice to have, with its own remembered locations, and
with the same merge/conflicts mechanism as regular commits.
** Affects: bzr (Ubuntu)
Importance: Undecided
Status: New
--
sync of uncommitted code between 2 computers
https://bugs.launchpad.net/bugs/263611
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
