summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorErich Keane <erich.keane@intel.com>2019-01-16 16:59:11 +0000
committerErich Keane <erich.keane@intel.com>2019-01-16 16:59:11 +0000
commitceebb7fe4905235f2e01ca495c5a43512c9a4edb (patch)
tree3aad5501c924057051b79ae0e3dd7a26329d0712
parent6640ca9634d97c07c5321c78e888cc6e197e64fe (diff)
Remove misleading line about git's lack of revision numbers.
Change-Id: I8a22cb4b4bef9bceee1f43381435d664c2cfd770
-rw-r--r--llvm/docs/Proposals/GitHubMove.rst4
1 files changed, 1 insertions, 3 deletions
diff --git a/llvm/docs/Proposals/GitHubMove.rst b/llvm/docs/Proposals/GitHubMove.rst
index f12077504db..5b68bac7056 100644
--- a/llvm/docs/Proposals/GitHubMove.rst
+++ b/llvm/docs/Proposals/GitHubMove.rst
@@ -105,8 +105,7 @@ A single revision number (e.g. r123456) thus identifies a consistent version of
all LLVM sub-projects.
Git does not use sequential integer revision number but instead uses a hash to
-identify each commit. (Linus mentioned that the lack of such revision number
-is "the only real design mistake" in Git [TorvaldRevNum]_.)
+identify each commit.
The loss of a sequential integer revision number has been a sticking point in
past discussions about Git:
@@ -860,7 +859,6 @@ References
.. [LattnerRevNum] Chris Lattner, http://lists.llvm.org/pipermail/llvm-dev/2011-July/041739.html
.. [TrickRevNum] Andrew Trick, http://lists.llvm.org/pipermail/llvm-dev/2011-July/041721.html
.. [JSonnRevNum] Joerg Sonnenberg, http://lists.llvm.org/pipermail/llvm-dev/2011-July/041688.html
-.. [TorvaldRevNum] Linus Torvald, http://git.661346.n2.nabble.com/Git-commit-generation-numbers-td6584414.html
.. [MatthewsRevNum] Chris Matthews, http://lists.llvm.org/pipermail/cfe-dev/2016-July/049886.html
.. [submodules] Git submodules, https://git-scm.com/book/en/v2/Git-Tools-Submodules)
.. [statuschecks] GitHub status-checks, https://help.github.com/articles/about-required-status-checks/