Hi Ingolemo, sorry you patch lingered for a while. It looks ok to me!
One thing is that I feel the description of the update button could be improved. You now write "Update the current branch" but what actually happens is that the files in the working tree are updated according to the info found in the branch (which can be the .bzr folder or in the case of a checkout from a remote branch from the remote .bzr folder). Changes made to the files which were not yet committed are kept and can be either discarded with Revert or committed.
So maybe a better description is "Update the files from the branch" or even "Update the working tree" as both lines are only understandable to a user who at least understands the difference between the working tree (the actual files under version control) and the branch (the info/files in the (remote) .bzr folder).
Hi Ingolemo, sorry you patch lingered for a while. It looks ok to me!
One thing is that I feel the description of the update button could be improved. You now write "Update the current branch" but what actually happens is that the files in the working tree are updated according to the info found in the branch (which can be the .bzr folder or in the case of a checkout from a remote branch from the remote .bzr folder). Changes made to the files which were not yet committed are kept and can be either discarded with Revert or committed.
So maybe a better description is "Update the files from the branch" or even "Update the working tree" as both lines are only understandable to a user who at least understands the difference between the working tree (the actual files under version control) and the branch (the info/files in the (remote) .bzr folder).
Regards,
Jasper