Hi Anton, thanks for taking the time to triage this bug report. I am a bit puzzled by your response though.
reportbug very clearly states that data loss warrants either 'grave' (which I selected) or 'critical' severity depending on whether it is recoverable or not. The release policy document for Wheezy [1] follows the same spirit except that it differentiates non-serious and serious data loss. Neither appear to support the idea that data loss would be 'wishlist' severity. I guess that would be like saying "You expect us to handle your data responsibly? Wishful thinking..." after all. Certainly not the message you intend to send to your users, right? From a user's perspective very very few things are worse than data loss. Personally, I rely on Ctrl-R (reverse-search-history) a lot. In a sense, erasing my .bash_history is like chopping off half of my keyboard. Often, I will also have little scripts in my .bash_history that I forgot to save in a proper script file or simply have not got around to doing so. Finally, note that this is not a very rare situation to happen. I routinely run out of quota at work every couple of weeks, when running data-intense experiments every couple of days. I have lost my bash history there too. I just never had the time to report the problem when it occurred before. Cheers, Rene [1] http://release.debian.org/testing/rc_policy.txt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
