Lines Matching full:revision
19 This is a proposal to move our current revision control system from our own
100 On Managing Revision Numbers with Git
104 A single revision number (e.g. r123456) thus identifies a consistent version of
107 Git does not use sequential integer revision number but instead uses a hash to
110 The loss of a sequential integer revision number has been a sticking point in
124 However, Git can emulate this increasing revision number:
129 We can thus use this revision number to ensure that e.g. `clang -v` reports a
130 user-friendly revision number (e.g. `main-12345` or `4.0-5321`), addressing
234 the sub-projects move synchronously, and a single revision number (or commit
377 Let's look how to assemble llvm+clang+libcxx at a given revision.
384 svn co https://llvm.org/svn/llvm-project/llvm/trunk llvm -r $REVISION
386 svn co https://llvm.org/svn/llvm-project/clang/trunk clang -r $REVISION
388 svn co https://llvm.org/svn/llvm-project/libcxx/trunk libcxx -r $REVISION
421 revision, which makes this straightforward::
425 git checkout $REVISION
442 the umbrella repo's updater bot to group all of them into a single revision.
508 SVN does not have builtin bisection support, but the single revision across
513 to synchronize the clang repository to match the llvm revision.