Comment 3 for bug 395906
Revision history for this message
| Martin Pool (mbp) wrote Re: bzr merge crashes on erroneous command line args: NoSuchRevision exception | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Guy,
It's not exactly that the last argument is mandatory and we crash when it's not given. Rather, merge with no path specified means to merge from the default location, typically your parent branch. That branch doesn't contain the revision you named therefore you get this error.
In many cases it does indicate an actual internal error, but with -r revid: obviously you can provoke it at will.
Options:
- NoSuchRevision should just give an error rather than a traceback, with the traceback being logged to ~/.bzr.log.
- NoSuchRevision remains as it is, but it's specially treated as a user error if encountered when looking up a revision spec.
- Possibly bzr merge should not have a default source; it's neither so obvious nor so necessary as for push and pull.