<div dir="ltr"><div class="gmail_extra">I've envisioned basically the same feature before, but I don't find the comments to be particularly useful without the complete context.</div><div class="gmail_extra"><br></div><div class="gmail_extra">What I really want from gerrit is a 3-way diff, wherein the first column is always the original state of the repo, the second column is a user-selectable patchset between (patchset 1) and (latest patchset - 1), and the third column is always the (latest patchset). And then make it easy for me to switch the middle column to a different patchset, without scrolling back to the top of the page. You'd be able to quickly skim through the history of comments and see the evolution of a patch, which I think is the same user experience that you're looking for?</div><div class="gmail_extra"><br></div><div class="gmail_extra">I agree with Jeremy though, this is ideally an upstream effort to improve gerrit itself.</div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 16, 2014 at 4:27 AM, Radoslav Gerganov <span dir="ltr"><<a href="mailto:rgerganov@vmware.com" target="_blank">rgerganov@vmware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I never liked how Gerrit is displaying inline comments and I find it hard to follow discussions on changes with many patch sets and inline comments. So I tried to hack together an html view which display all comments grouped by patch set, file and commented line. You can see the result at <a href="http://gerrit-mirror.appspot.com/" target="_blank">http://gerrit-mirror.appspot.<u></u>com/</a><change-id>. Some examples:<br>
<br>
<a href="http://gerrit-mirror.appspot.com/127283" target="_blank">http://gerrit-mirror.appspot.<u></u>com/127283</a><br>
<a href="http://gerrit-mirror.appspot.com/128508" target="_blank">http://gerrit-mirror.appspot.<u></u>com/128508</a><br>
<a href="http://gerrit-mirror.appspot.com/83207" target="_blank">http://gerrit-mirror.appspot.<u></u>com/83207</a><br>
<br>
There is room for many improvements (my css skills are very limited) but I am just curious if someone else finds the idea useful. The frontend is using the same APIs as the Gerrit UI and the backend running on GoogleAppEngine is just proxying the requests to <a href="http://review.openstack.org" target="_blank">review.openstack.org</a>. So in theory if we serve the html page from our Gerrit it will work. You can find all sources here: <a href="https://github.com/rgerganov/gerrit-hacks" target="_blank">https://github.com/rgerganov/<u></u>gerrit-hacks</a>. Let me know what you think.<br>
<br>
Thanks,<br>
Rado<br>
<br>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
</blockquote></div><br></div></div>