Feature Request: qlog for entire branch/checkout of selected project
Bug #386672 reported by
Craig Hewetson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
QBzr-Eclipse Plugin |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
A qlog for the entire branch/checkout of the selected project would be very useful. (If the option is there then I must be missing something.)
Not sure of the best solution, maybe the two actions in the menu:
log...
log branch/checkout...
Related branches
lp:~craighewetson-deactivatedaccount/qbzr-eclipse/menuActions
Merged
into
lp:qbzr-eclipse
- Nicholas Allen: Approve
-
Diff: 159 lines4 files modifiedqbzr-eclipse/plugin.xml (+25/-5)
qbzr-eclipse/src/org/bazaar_vcs/qbzr_eclipse/handlers/BazaarCommandHandler.java (+15/-5)
qbzr-eclipse/src/org/bazaar_vcs/qbzr_eclipse/handlers/DiffMenuCommandHandler.java (+10/-0)
qbzr-eclipse/src/org/bazaar_vcs/qbzr_eclipse/handlers/LogMenuCommandHandler.java (+10/-0)
Changed in qbzr-eclipse: | |
assignee: | nobody → Craig Hewetson (craighewetson) |
importance: | Undecided → Wishlist |
status: | New → Confirmed |
Changed in qbzr-eclipse: | |
status: | Confirmed → Fix Committed |
Changed in qbzr-eclipse: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
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.