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 #7 by trowbrds:
After discussing this with Christian, I'm going to say that we're not going
to change
this behavior. If you change
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 #8 by amordkov:
Please note that, as per comment #2, the title of the bug should
be Posting a new
diff against a changeset for
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 #9 by chipx86:
I may be changing Discard down the road but that's just a label. It's not
the same
as deleting (admins actually have
Issue 581: Dashboard defaults to Incoming Reviews, not last viewed box
http://code.google.com/p/reviewboard/issues/detail?id=581
Comment #2 by trowbrds:
Keeping state like this is tricky unless we plumb it through the views
somehow. It's
really easy for things to get weird if you're working
Issue 598: Enhancement: Editing the people field to add reviewers should
look at both the user id and First/Last names
http://code.google.com/p/reviewboard/issues/detail?id=598
Comment #2 by trowbrds:
(No comment was entered for this change.)
Issue attribute updates:
Status:
Issue 581: Dashboard defaults to Incoming Reviews, not last viewed box
http://code.google.com/p/reviewboard/issues/detail?id=581
Comment #3 by chipx86:
Or just store a cookie and return the appropriate view based on that value,
making it
work like a query parameter.
--
You received this
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 #10 by amordkov:
I think it's not uncommon for a developer to want to really 'discard' diffs
that they
had uploaded, so that
