<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 6 October 2016 at 11:54, Fan Xin <span dir="ltr"><<a href="mailto:fan.xin@jp.fujitsu.com" target="_blank">fan.xin@jp.fujitsu.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Delete because they've all been merged upstream, or because they<br>
conflict and you don't want to rebase?<br>
<br>
</blockquote>
Delete the unnecessary patch files because<br></span>
1. Some of patch files have been merged into upstream.<br>
2. Upstream drop some test cases where these patch adapt to, so the patch files become unnecessary and nowhere to adapt.</blockquote><div><br></div><div>Please list these in the commit message.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The patches I looked at either had no or pending Upstream-Status, so I<br>
can't trivially check that they have been submitted upstream and are now<br>
redundant.<br>
</blockquote>
<br></span>
Did you mean that Upstream-Status should be added for each patch file ?<br></blockquote></div><br>For all remaining patches that would be very useful, so we can identify patches which are backports / inappropriate for upstream / should be submitted upstream.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>