From: Andreas Schuh <andreas.schuh.84@gmail.com>
Date: Fri, 25 Nov 2016 18:10:19 +0000 (+0000)
Subject: doc: Update use of gflags with Bazel documentation
X-Git-Tag: accepted/tizen/5.0/unified/20181102.024438~29
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=84ab952375a06404902f4a9b96d6a7a731214503;p=platform%2Fupstream%2Fgflags.git

doc: Update use of gflags with Bazel documentation
---

diff --git a/INSTALL.md b/INSTALL.md
index e3a23c8..d37528f 100644
--- a/INSTALL.md
+++ b/INSTALL.md
@@ -73,14 +73,14 @@ To use gflags in a Bazel project, map it in as an external dependency by editing
 your WORKSPACE file:
 
     git_repository(
-        name = "gflags_git",
-        commit = "",  # Use the current HEAD commit
+        name = "com_github_gflags_gflags",
+        commit = "<INSERT COMMIT SHA HERE>",
         remote = "https://github.com/gflags/gflags.git",
     )
 
     bind(
         name = "gflags",
-        actual = "@gflags_git//:gflags",
+        actual = "@com_github_gflags_gflags//:gflags",
     )
 
 You can then add `//external:gflags` to the `deps` section of a `cc_binary` or
diff --git a/doc b/doc
index ea1cc83..78c66b3 160000
--- a/doc
+++ b/doc
@@ -1 +1 @@
-Subproject commit ea1cc83b50dc44df1f38891d9c95e99e2f127a80
+Subproject commit 78c66b37266707a3cf2904c3891b08cddae8d83e