What do you think should be the desired behaviour?
Currently it checks:
1) -t option (if yes, it uses that)
2) if local branch is named "review/%s/%s" then it uses the last string component
3) searches for bug or lp number
4) searches for blueprint ("bp") number
5) uses local branch name as it is
When checking out the change with "-d", local branch gets set to "review/<author>/<change-number>" or "review/<author>/<change-number>-patch<patchset-number>"
What do you think should be the desired behaviour?
Currently it checks:
1) -t option (if yes, it uses that)
2) if local branch is named "review/%s/%s" then it uses the last string component
3) searches for bug or lp number
4) searches for blueprint ("bp") number
5) uses local branch name as it is
When checking out the change with "-d", local branch gets set to "review/ <author> /<change- number> " or "review/ <author> /<change- number> -patch< patchset- number> "