Repository: hadoop
Updated Branches:
  refs/heads/branch-2.8 f9d3bb3b8 -> e47c95ffb


HADOOP-14268. Fix markdown itemization in hadoop-aws documents. Contributed by 
Akira Ajisaka


Project: http://git-wip-us.apache.org/repos/asf/hadoop/repo
Commit: http://git-wip-us.apache.org/repos/asf/hadoop/commit/e47c95ff
Tree: http://git-wip-us.apache.org/repos/asf/hadoop/tree/e47c95ff
Diff: http://git-wip-us.apache.org/repos/asf/hadoop/diff/e47c95ff

Branch: refs/heads/branch-2.8
Commit: e47c95ffbfcfdefc7bfe4fb01733885c649ce1d1
Parents: f9d3bb3
Author: Mingliang Liu <[email protected]>
Authored: Mon Apr 3 11:15:03 2017 -0700
Committer: Mingliang Liu <[email protected]>
Committed: Mon Apr 3 11:15:03 2017 -0700

----------------------------------------------------------------------
 hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/index.md | 1 +
 1 file changed, 1 insertion(+)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/hadoop/blob/e47c95ff/hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/index.md
----------------------------------------------------------------------
diff --git 
a/hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/index.md 
b/hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/index.md
index 334635d..5fe0d91 100644
--- a/hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/index.md
+++ b/hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/index.md
@@ -91,6 +91,7 @@ access to the data. Anyone with the credentials can not only 
read your datasets
 —they can delete them.
 
 Do not inadvertently share these credentials through means such as
+
 1. Checking in to SCM any configuration files containing the secrets.
 1. Logging them to a console, as they invariably end up being seen.
 1. Defining filesystem URIs with the credentials in the URL, such as


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to