<blockquote>
<p>...poor <a href="https://github.com/b4n" class="user-mention">@b4n</a> really can't be expected to review it. There has got to be a better way, what about doing the whitespace first then? That will have no code changes and would be more reasonably reviewable and could even be a few files at a time.</p>
</blockquote>

<p>Reviewing it through "Files changed" would be crazy and would indeed be unreviewable. But it can be easily reviewed patch by patch - if you simply click the whitespace patch above, you get</p>

<p><a href="https://github.com/geany/geany/pull/1160/commits/6bc579798716dbe94a171a016f9989c92c4b67e2" class="commit-link"><tt>6bc5797</tt></a></p>

<p>which is quite obvious (well, the github diff implementation screws up from time to time and doesn't show the same lines next to each other but there are not so many of those). Reviewing the patches individually is the same as if I created several pull requests (which isn't easily doable because of the patch dependency as I explained).</p>

<p>So I hope our poor old <a href="https://github.com/b4n" class="user-mention">@b4n</a> won't suffer much :-).</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/geany/geany/pull/1160#issuecomment-237513070">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJxWIzVf3lBqAQt0j7iG86hF3ydjnks5qcbw6gaJpZM4JbITK">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABDrJ9SR3QhF_xlJ9DQ-JNiVx5r1NEGqks5qcbw6gaJpZM4JbITK.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/geany/geany/pull/1160#issuecomment-237513070"></link>
  <meta itemprop="name" content="View Pull Request"></meta>
</div>
<meta itemprop="description" content="View this Pull Request on GitHub"></meta>
</div>

<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/geany/geany","title":"geany/geany","subtitle":"GitHub repository","main_image_url":"https://assets-cdn.github.com/images/modules/aws/aws-bg.jpg","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/geany/geany"}},"updates":{"snippets":[{"icon":"PERSON","message":"@techee in #1160: \u003e ...poor @b4n really can't be expected to review it. There has got to be a better way, what about doing the whitespace first then? That will have no code changes and would be more reasonably reviewable and could even be a few files at a time.\r\n\r\nReviewing it through \"Files changed\" would be crazy and would indeed be unreviewable. But it can be easily reviewed patch by patch - if you simply click the whitespace patch above, you get\r\n\r\nhttps://github.com/geany/geany/pull/1160/commits/6bc579798716dbe94a171a016f9989c92c4b67e2\r\n\r\nwhich is quite obvious (well, the github diff implementation screws up from time to time and doesn't show the same lines next to each other but there are not so many of those). Reviewing the patches individually is the same as if I created several pull requests (which isn't easily doable because of the patch dependency as I explained).\r\n\r\nSo I hope our poor old @b4n won't suffer much :-).\r\n"}],"action":{"name":"View Pull Request","url":"https://github.com/geany/geany/pull/1160#issuecomment-237513070"}}}</script>