On Wed, Jul 29, 2009 at 9:35 AM, Chris Szikszoy<[email protected]> wrote: >>> There is an open bug about this, if you'd like to "Me too" it: >>> >>> https://bugs.edge.launchpad.net/launchpad-code/+bug/385255 >> >> That bug kind of confuses me. I understand Brian's original post, but >> I don't understand how that bug represents the same problem. I have >> the problem that Brian does: I can't tell when I need to re-review a >> branch. Is there a bug that more precisely reflects this use case? >> >> >> -- >> Christopher Armstrong >> http://radix.twistedmatrix.com/ >> http://planet-if.com/ >> http://canonical.com/ >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~launchpad-users >> Post to : [email protected] >> Unsubscribe : https://launchpad.net/~launchpad-users >> More help : https://help.launchpad.net/ListHelp >> > > Hello, > > Perhaps this is more relevant. > https://bugs.edge.launchpad.net/launchpad-code/+bug/392343 > This is a bug I filed about Launchpad not updating the merge diff > after new revisions were added to the branch after the review was > initially requested. To go along with this, it would be nice if I > could specify that a certain revision is in response to a particular > merge review comment. We already have the "--fixes=..." option for > bugs. Perhaps we could use that option to reference a particular > launchpad review comment, then the reviewer or whoever made that > comment could be automatically notified by email when I commit a new > revision to the branch being reviewd. > > - Chris Szikszoy > [email protected] >
Sorry, I forgot to CC lp-users. - Chris _______________________________________________ Mailing list: https://launchpad.net/~launchpad-users Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-users More help : https://help.launchpad.net/ListHelp
