<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 Jul 26, 2016, at 9:46 AM, Tim Northover <<a href="mailto:t.p.northover@gmail.com" class="">t.p.northover@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On 26 July 2016 at 09:36, Mehdi Amini via llvm-dev<br class=""><<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>> wrote:<br class=""><blockquote type="cite" class="">It is possible to continue adding the equivalent of git-svn-id in the commit message if it is what you’re referring to.<br class=""></blockquote><br class="">Wouldn't that rely on people installing the correct post-commit (pre?)<br class="">hooks locally?<br class=""></div></div></blockquote></div><br class=""><div class="">I’ll clarify: with Justin’s monorepo proposal we would have a single repository with all the llvm-projects inside.</div><div class="">There is a natural cross-project synchronization since we share the repository.</div><div class=""><br class=""></div><div class="">While this repository would be the “source-of-truth” like SVN is today, and be read-write for developers, we would be able to continue to update the separate existing read-only repositories (<a href="http://llvm.org/git/llvm.git" class="">http://llvm.org/git/llvm.git</a> <a href="http://llvm.org/git/clang.git" class="">http://llvm.org/git/clang.git</a> etc.).</div><div class=""><br class=""></div><div class="">When exporting a commit from the monorepo to one of the read-only repository, it should be possible to generate a “git-svn-id”-like the same way we’re doing when exporting from SVN today.</div><div class=""><br class=""></div><div class="">Make sense?</div><div class=""><br class=""></div><div class="">— </div><div class="">Mehdi</div><div class=""><br class=""></div></body></html>