<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 8, 2016, at 10:32 AM, <a href="mailto:dag@cray.com" class="">dag@cray.com</a> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Mehdi Amini <<a href="mailto:mehdi.amini@apple.com" class="">mehdi.amini@apple.com</a>> writes:<br class=""><br class=""><blockquote type="cite" class=""> It could be problematic for us depending on how the monorepository<br class=""> is structured. We reference the LLVM git repository directly and<br class=""> use it to migrate to new versions, pick patches, etc. If LLVM<br class=""> proper were part of a larger repository that becomes more<br class=""> difficult to do because the commit file paths won't match. We'd be<br class=""> back to essentially manual diff+patch which is quite a step<br class=""> backward from the smoth git-oriented process we use now.<br class=""><br class="">Can you clarify what you mean? Which part of the process would quite<br class="">manual patch that wouldn’t otherwise?<br class=""></blockquote><br class="">If the monorepository is not using submodules but is instead a weaving<br class="">of the histories of each component, that means each tree item pointing<br class="">to a blob will have a different path. For example,<br class="">lib/Target/X86/X86InstrInfo.cpp would become<br class="">llvm/lib/Target/X86/X86InstrInfo.cpp or something similar. IME git<br class="">doesn't deal well with applying changes to blobs that exist in different<br class="">paths in the repository. That makes sense since the hashes directly<br class="">depend on the information in the trees.<br class=""><br class=""><blockquote type="cite" class=""> The document says that the individual git repositories will<br class=""> remain. Does that mean the monorepository is using git-submodule<br class=""> to manage the aggregate repository?<br class=""><br class="">First, have you read this document: <a href="https://reviews.llvm.org/D24167" class="">https://reviews.llvm.org/D24167</a> ?<br class=""></blockquote><br class="">Yes, though I was only able to figure out how to see an actual document<br class="">by clicking "download raw diff." I'm not sure that's giving me the<br class="">latest version. Is there another convenient way to view the document,<br class="">preferable with the Markdown rendered?<br class=""></div></div></blockquote><div><br class=""></div><div>Sure, what about a PDF?</div><div><br class=""></div><div></div></div></body></html>