From 1af7ee01d9d6d394078fe5343d820a5cf8b4f93c Mon Sep 17 00:00:00 2001 From: chentao1596 Date: Fri, 2 Dec 2016 09:54:16 +0800 Subject: [PATCH] make modifications for README --- staging/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/staging/README.md b/staging/README.md index af3ed93c5975c..9a81c7ba574b3 100644 --- a/staging/README.md +++ b/staging/README.md @@ -1,3 +1,3 @@ -This _staging/src/k8s.io/client-go directory is the staging area of the client repo. It contains a versioned client, tools built around the client like the reflector, and all the client dependencies. The content will be periodically published to k8s.io/client-go repo. -The staged content is copied from the main repo, i.e., k8s.io/kubernetes, with directory rearrangement and necessary rewritings. To sync the content with the latest code in your local k8s.io/kubernetes, you need to run `godep restore` in k8s root directory, then run _staging/src/k8s.io/client-go/copy.sh. +This staging/src/k8s.io/client-go directory is the staging area of the client repo. It contains a versioned client, tools built around the client like the reflector, and all the client dependencies. The content will be periodically published to k8s.io/client-go repo. +The staged content is copied from the main repo, i.e., k8s.io/kubernetes, with directory rearrangement and necessary rewritings. To sync the content with the latest code in your local k8s.io/kubernetes, you need to run `godep restore` in k8s root directory, then run staging/copy.sh. vendor/k8s.io/client-go is a symlink pointing to this staging area, so to use the packages in the staging area, you can import it as "vendor/client-go/", as if the client were vendored. The client will be vendored from k8s.io/client-go for real after the test matrix is converted to vendor k8s components.