<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 Oct 12, 2016, at 3:42 PM, Duncan P. N. Exon Smith <<a href="mailto:dexonsmith@apple.com" class="">dexonsmith@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><blockquote type="cite" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class=""><br class="Apple-interchange-newline">On 2016-Oct-12, at 15:24, Mehdi Amini <<a href="mailto:mehdi.amini@apple.com" class="">mehdi.amini@apple.com</a>> wrote:<br class=""><br class=""><blockquote type="cite" class=""><br class="">On Oct 12, 2016, at 3:11 PM, Duncan P. N. Exon Smith <<a href="mailto:dexonsmith@apple.com" class="">dexonsmith@apple.com</a>> wrote:<br class=""><br class=""><br class=""><blockquote type="cite" class="">On 2016-Oct-12, at 14:54, Mehdi Amini <<a href="mailto:mehdi.amini@apple.com" class="">mehdi.amini@apple.com</a>> wrote:<br class=""><br class=""><blockquote type="cite" class=""><blockquote type="cite" class="">+ * Refactoring across projects is not frienly: taking some functions from clang<br class=""></blockquote><br class="">s/frienly/friendly/<br class=""><br class=""><blockquote type="cite" class="">+ to make it part of a utility in libSupport wouldn't carry the history of the<br class="">+ code in the llvm repo, preventing recursively applying `git blame` for<br class="">+ instance.<br class=""></blockquote><br class="">Please add: "However, this is no different than the current state.”<br class=""></blockquote><br class="">I can compromise with "However, this is not very different than the current state.”<br class=""><br class="">Although today I can move code across subproject in a single commit and git blame works in the monorepo export.<br class=""><br class=""></blockquote><br class="">I'm convinced you could set up a monorepo mirror even if the canonical source uses multirepo.<br class=""></blockquote><br class="">Sure, but aggregating the individual repo does not bring the possibility to have a single commit in the aggregation repo that moves code across the original sub-repo, while now you can (the canonical repository supports it).<span class="Apple-converted-space"> </span><br class=""><br class="">I’m skeptical that tooling can really help in practice with this (outside of limited trivial cases).<br class=""><br class=""><blockquote type="cite" class="">The current state is: multiple subproject refactorings are not friendly (require heavy tooling). Adopting multirepo doesn't change that much. It will still be unfriendly, but require heavy tooling.<br class=""><br class="">How about: "However, this is similar to the current state."?<br class=""></blockquote></blockquote><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">Let me repeat:</span><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">How about: "However, this is similar to the current state.”?</span></div></blockquote><br class=""></div><div>Let’s look at the full paragraph, I’d write:</div><div><font color="#5856d6" class=""><br class=""></font></div><div><div>Refactoring across projects is not friendly: taking some functions from clang</div><div>to make it part of a utility in libSupport wouldn't carry the history of the</div><div>code in the llvm repo, preventing recursively applying `git blame` for</div><div>instance. However, this is not very different than how most people are</div><div>Interacting with the repository today, by splitting such change in multiple</div><div>commits.</div></div><div class=""><br class=""></div></body></html>