[SYCL][Doc] Prepare for extension revisions

[mkinsner]

Prepare for extension update - fork implemented version so that ready for repo reorganization into "implemented" and "proposed" categories

Signed-off-by: Michael Kinsner michael.kinsner@intel.com

[gmlueck]

I assume your plan is to modify the original files (e.g. "data_flow_pipes.asciidoc") now that you have created "data_flow_pipes_implemented.asciidoc". However, this will cause problems because the README.md file will point to the version of the file that is not yet implemented ("data_flow_pipes.asciidoc").

I think it would be better to copy these files to something like "data_flow_pipes-rev2-proposed.asciidoc", and then modify the copy. That way the README continue to point to the implemented version.

[mkinsner]

I assume your plan is to modify the original files (e.g. "data_flow_pipes.asciidoc") now that you have created "data_flow_pipes_implemented.asciidoc". However, this will cause problems because the README.md file will point to the version of the file that is not yet implemented ("data_flow_pipes.asciidoc").

I think it would be better to copy these files to something like "data_flow_pipes-rev2-proposed.asciidoc", and then modify the copy. That way the README continue to point to the implemented version.

I was trying to prevent someone else needing to rebase, but good point on the links. I changed to reflect your suggestion.