bzr push/pull/missing: branches are diverged message should be improved for completely unrelated branches
Bug #157027 reported by
Alexander Belchenko
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Low
|
Unassigned | ||
Breezy |
Triaged
|
Low
|
Unassigned |
Bug Description
From my RFC-email to bzr ML:
Today my coworker ran in very funny and ugly situation.
He wanted to pull changes from some branch, and `bzr pull`
said that branches are diverged. When I suggest to run
`bzr missing` we saw veeeery looong output because
these branches was unrelated at all (he by mistake
cd to different project). I.e. these branches are completely
different, but yes, they probably diverged in the sense
of English words (I'm not sure here).
IMO, in this situation it's better if bzr says that branches
completely different so user can understand his own mistake
faster.
tags: | added: check-for-breezy |
Changed in brz: | |
status: | New → Triaged |
importance: | Undecided → Low |
tags: |
added: error-reporting removed: check-for-breezy |
To post a comment you must log in.
In replies to my e-mail people are agree that it should be improved.