Move content/components/navigation_interception to src/components

content/components/README

Index: content/components/README
diff --git a/content/components/README b/content/components/README
deleted file mode 100644
index 00266a71a7f9e36008c5c6d3f1865176087bac00..0000000000000000000000000000000000000000
--- a/content/components/README
+++ /dev/null
@@ -1,50 +0,0 @@
-=============== BLINK BLINK BLINK ===============
-=============== BLINK BLINK BLINK ===============
-
-Warning: The decision has been made that the new home for components
-that depend on the Content Module and layers below it is
-src/components/. Full details at
-http://www.chromium.org/developers/design-documents/browser-components
-
-The components currently in src/content/components/
-(this directory) will be moving there. Talk to joi@chromium.org for
-coordination if you are creating a new component.
-
-=============== BLINK BLINK BLINK ===============
-=============== BLINK BLINK BLINK ===============
-
-
-This directory is for components that have the Content Module as the
-uppermost layer they depend on.  They may depend only on the Content
-API (content/public) and on lower layers (e.g. base/, net/, ipc/
-etc.).
-
-These components are not part of the Content Module itself.  They are
-built in a separate .gyp file (content_components.gyp in this
-directory).
-
-Components that have bits of code that need to live in different
-processes (e.g. some code in the browser process, some in the renderer
-process, etc.) should separate the code into different subdirectories.
-Hence for a component named 'foo' you might end up with a structure
-like the following:
-
-content/components/foo          - DEPS, OWNERS, foo.gypi
-content/components/foo/browser  - code that needs the browser process
-content/components/foo/common   - for e.g. IPC constants and such
-content/components/foo/renderer - code that needs renderer process
-
-These subdirectories should have DEPS files with the relevant
-restrictions in place, e.g. only content/components/foo/browser should
-be allowed to #include from content/public/browser.
-
-Note that there may also be an 'android' subdir, with a Java source
-code structure underneath it where the package name is
-org.chromium.content.component.foo, and with subdirs after 'foo'
-to illustrate process, e.g. 'browser' or 'renderer':
-
-content/components/foo/android/OWNERS, DEPS
-content/components/foo/android/java/src/org/chromium/content/component/foo/browser/
-content/components/foo/android/javatests/src/org/chromium/content/component/foo/browser/
-
-Code in content/components/ should be placed in the content:: namespace.