<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">I assumed we want ids for the umbrella repository to ease bisection and having something to print as a version identifier, but do we really need them for the other repositories?</div><div class=""><br class=""></div><div class="">I also still don't see why `<span style="color: rgb(84, 84, 84); font-family: arial, sans-serif; font-size: small; background-color: rgb(255, 255, 255);" class="">git </span><span style="font-weight: bold; color: rgb(106, 106, 106); font-family: arial, sans-serif;" class="">rev-list</span><span style="color: rgb(84, 84, 84); font-family: arial, sans-serif; font-size: small; background-color: rgb(255, 255, 255);" class=""> --count --all` does not work. Sure the count is only per branch, but why would ever need to have continuous numbering between say a 3.8.XX revision and a 3.9.XX branch...</span></div><div class=""><span style="color: rgb(84, 84, 84); font-family: arial, sans-serif; font-size: small; background-color: rgb(255, 255, 255);" class=""><br class=""></span></div><div class=""><span style="color: rgb(84, 84, 84); font-family: arial, sans-serif; font-size: small; background-color: rgb(255, 255, 255);" class="">- Matthias</span></div><br class=""><div><blockquote type="cite" class=""><div class="">On Jun 30, 2016, at 9:33 AM, Reid Kleckner via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote">On Thu, Jun 30, 2016 at 9:16 AM, James Y Knight via lldb-dev <span dir="ltr" class=""><<a href="mailto:lldb-dev@lists.llvm.org" class="">lldb-dev@lists.llvm.org</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr" class="">I don't think we should do any of that. It's too complicated -- and I don't see the reason to even do it.<div class=""><br class=""></div><div class="">There's a need for the "llvm-project" repository -- that's been discussed plenty -- but where does the need for a separate "id" that must be pushed into all of the sub-projects come from? This is the first I've heard of that as a thing that needs to be done.</div><div class=""><br class=""></div><div class="">There was a previous discussion about putting an sequential ID in the "llvm-project" repo commit messages (although, even that I'd say is unnecessary), but not anywhere else.</div></div></blockquote><div class=""><br class=""></div><div class="">Agreed, the llvm-project repository can completely take on the role of the SQL database in Renato's proposal.</div><div class=""><br class=""></div><div class="">Chromium created a "git-number" extension that assigns sequential ids to commits in the obvious way, and that provided some continuity with the "git-svn-id:" footers in commit messages. I'm not sure their extension is particularly reusable, though:</div><div class=""><a href="https://chromium.googlesource.com/chromium/tools/depot_tools.git/+/master/git_number.py" class="">https://chromium.googlesource.com/chromium/tools/depot_tools.git/+/master/git_number.py</a><br class=""></div><div class=""><br class=""></div><div class="">I think for LLVM, whatever process updates the umbrella repo should add the sequential IDs to the commit message, and that will help provide continuity across the git/svn bridge.</div></div></div></div>
_______________________________________________<br class="">LLVM Developers mailing list<br class=""><a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a><br class="">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev<br class=""></div></blockquote></div><br class=""></body></html>