Comment 1 for bug 386672
Revision history for this message
| Craig Hewetson (craighewetson-deactivatedaccount) wrote | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
4d1350f
(Get the code!)
The log feature becomes real pain on large projects where multiple projects from the same branch are in a eclipse workspace. The user doesn't want to execute bzr qlog <dir> accidentally (since it takes minutes to display results, in my case.)
I recommend that the main menu's "Log History" action (and maybe most of the other actions) behave slightly differently from the right click actions. ie If the main menu actions are executed they apply to the BRANCH of the last project selected and not the sub directory that the project might represent.
Where as the right click actions must continue to work as they currently do. Expect actions like update that always applies to the branch of a selected resource. i.e bzr update <file> doesn't really mean anything within a branch.
Since this is a major change, I don't want to start doing anything unless its been discussed. So let me know if it makes sense and if its applicable to your workflow scenarios.