<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Sep 9, 2015, at 1:31 PM, Glyph Lefkowitz <<a href="mailto:glyph@twistedmatrix.com" class="">glyph@twistedmatrix.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Sep 9, 2015, at 7:51 AM, Adi Roiban <<a href="mailto:adi@roiban.ro" class="">adi@roiban.ro</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">Is there anybody still using the diffresource links in Trac tickets?<br class=""><br class="">If you are still using it, do you think you can use the GitHub diff instead?<br class=""><br class="">Can we remove it from Trac?<br class=""><br class="">I prefer the GitHub diff as I can use side-by-side view and expand the<br class="">diff or go to full file.<br class=""><br class="">Here is the associated ticket <a href="https://github.com/twisted-infra/braid/issues/102" class="">https://github.com/twisted-infra/braid/issues/102</a><br class=""></div></blockquote></div><br class=""><div class="">I still use it sometimes to apply the current patch to a working copy: quicker to type the URL.</div><div class=""><br class=""></div></div></div></blockquote><div><br class=""></div><div>Not sure if you know this, but if you click the “github” link under the branch name, and then add “.patch” to the end of a URL, you get a patch file that you can apply to a working copy.<br class=""></div><div><br class=""></div><div class=""><br class=""></div><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">That said I think that removing it is an acceptable regression for the git migration; it should be trivial to re-implement using git if anyone (including me) cares enough, and it should be substantially faster.</div><div class=""><br class=""></div></div></div></blockquote><div><br class=""></div><div>-radix</div></div></body></html>