Issue 559: Posting a new diff against a discarded changeset should create a new review request http://code.google.com/p/reviewboard/issues/detail?id=559
Comment #11 by chipx86: It's the developer's responsibility to view the diff before making it public. There's risks associated with actually deleting a diff. Any reviews, comments, anything associated with the diff will also go away, and then any replies based on those, etc. In the future when we have extensions, it could really break things if the code's expecting those diffs to be there. Same with actually deleting review requests. We have a very strict policy of not deleting history because things break when this happens. Developers can easily preview diffs and then replace them before publishing the draft, but once it's published, it's part of history. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "reviewboard-issues" group. To post to this group, send email to reviewboard-issues@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en -~----------~----~----~----~------~----~------~--~---
