Uncommited changes checked after downloading history
Bug #605091 reported by
Javier Collado
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| bzr-rewrite |
Fix Released
|
Low
|
Jelmer Vernooij | ||
Bug Description
When rebasing against a remote branch, it seems that bzr-rebase downloads the remote branch history and, after that, checks if the local branch has uncommitted changes in which case returns an error.
It would be better to check for uncommitted changes before downloading the remote branch history to provide a faster response in case the rebasing operation isn't possible because of uncommitted changes.
| Changed in bzr-rewrite: | |
| status: | New → Fix Committed |
| importance: | Undecided → Low |
| assignee: | nobody → Jelmer Vernooij (jelmer) |
| milestone: | none → 0.6.1 |
| tags: | added: verified |
| tags: | removed: verified |
| Changed in bzr-rewrite: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
