RFC: remove traceback from "newer branch format than your bzr"

[Jelmer Vernooij]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Samuel Bronson wrote:
> At Tue, 11 Aug 2009 15:14:45 +0200, Jelmer Vernooij wrote:
>
>> Strack traces are the equivalent of segmentation faults in
>> Bazaar, when they are displayed there is *always* a bug, never
>> expected behaviour. I think hiding the detailed debug information
>> here is a red herring, we should work on fixing those bugs
>> instead.
>
> Ever notice how on Windows, when you get an error like that, it
> usually only shows you a little bit of info? You have to click on
> things (or have a debugger installed) to get more out of it...
That seems like a reasonable approach for GUI's, but this is a
command-line interface.
>
> Also, even in Linux, I don't remember getting stack traces for
> segfaults very often...
And with C apps on Linux it's a big annoyance to have to ask users to
reproduce a problem when running inside of gdb or getting it to
produce a core file. I'd rather avoid having to do that for bzr.

Cheers,

Jelmer

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQIcBAEBAgAGBQJKgavkAAoJEACAbyvXKaRXijEP/iueg+NpBIwQsIoBxC/fC4Yu
to03mwV7PYMrQxG7dtbp7b31mcKnhmo3hJZMNqflvfm8y3HxgSkwS0lxoJQMKwe9
kdCFIkYroVtvbjWjMKAD0FIVe2LB/xg+iBIKDgwE1cEV5PHXIdajxdfa4+DWSV0j
0/W3awm1EfFZn4382isqp+DOo7mw3WL63IDI98R+y7sK+PI5r7UQ45cCROzi5KPz
eh9vRlAHFRGZxAy7zZA3izDBm1hJrc17SCYXdfQZVu1aaSX+g4agvj62sPbW3gmI
1lJhh7WCMw798PiHXZEtabe54FLDSffyxn6wmqhxGQRpnaPkPOjNgixcWOdhQ63m
1EaejjYvpFrGpOl3qQgREUETOGtfoEceCoN/UqUrW17WtY5mKyCii7gH33UX8coT
2AUPX/f5AAcJtHQxZ8/2awYf4nO1jaftOOAPyCjfUJ7AqIMnQ8KWhD8PRwHIwAFm
271+Nunykv1TkU6cmO66HZJattI9q6Z2/vkcuJU03y4z48IAwVrbdsIK9+FcMfDe
tsFvaFUvFPW1JBCQtZWVuOW5E8sgkDS2QWHG7ln9R31bOf9V36eXWpZuHolGzSvV
4J8qTg5uKwzBT7AV4/GZDKzguuTY4hyAXtQr76Mq0wf+c18DWO4rJiXGJGn3xmYp
+22jDPaiag0NjezRgAbM
=+uvQ
-----END PGP SIGNATURE-----