search for: llvmgit

...I could. Here's an updated version for review. I have some patches to commit and I'm going to try using the process in this document to root out bugs. -Dave -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: LLVMgit.txt URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110824/b8c8ae75/attachment.txt>

...path = tools/lldb url = ../lldb.git [submodule "tools/lld"] path = tools/lld url = ../lld.git I’ve attached a patch just in case this was the right way to go. Cheers, Kuba Ober -------------- next part -------------- A non-text attachment was scrubbed... Name: llvmgit.patch Type: application/octet-stream Size: 894 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140310/ef7dfc79/attachment.obj>

...workflow that works with the current review process. This is but one. We should add this to the web page once it's polished if we make the transition to git. -Dave -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: LLVMgit.txt URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110822/73f364d4/attachment.txt>

> On Aug 18, 2011, at 10:57 AM, David Greene wrote: >> >> Did the project ever come to a decision about making a transition to >> git? I'm trying to do some longer-term planning and it would be helpful >> to know what the roadmap is. It's stuck on: 1) A misunderstanding that global revision numbers are necessary and that 'git describe' along with