Restoring authorship annotation for Vlad Yaroslavlev <vladon@vladon.com>. Commit 1 of 2.

1 files changed, 14 insertions, 14 deletions

diff --git a/build/ymake.core.conf b/build/ymake.core.conf
index 081833998b..4d08923b19 100644
--- a/build/ymake.core.conf
+++ b/build/ymake.core.conf
@@ -1027,7 +1027,7 @@ macro GRPC() {
 
     # Java
     JAVA_PROTO_PLUGIN(grpc_java contrib/tools/protoc/plugins/grpc_java DEPS $JAVA_GRPC_STUB $JAVA_GRPC_PROTOBUF)
-}
+} 
 
 # tag:fbs
 FLATC_FLAGS_VALUE=
@@ -2034,7 +2034,7 @@ macro DISABLE_DATA_VALIDATION() {
 TEST_DATA_VALUE=
 ### @usage: DATA([path...])
 ###
-### Specifies the path to the data necessary test.
+### Specifies the path to the data necessary test. 
 ### Valid values are: arcadia/<path> , arcadia_tests_data/<path> and sbr://<resource_id>.
 ### In the latter case resource will be brought to the working directory of the test before it is started
 ###
@@ -4694,7 +4694,7 @@ macro ANNOTATION_PROCESSOR(Args...) {
 EXCLUDE_VALUE=
 ### EXCLUDE(prefixes)
 ###
-### The macro is in development.
+### The macro is in development. 
 ### Specifies which libraries should be excluded from the classpath.
 macro EXCLUDE(Args...) {
     SET_APPEND(EXCLUDE_VALUE $ARGS_DELIM $Args)
@@ -4709,7 +4709,7 @@ JAVA_SRCS_VALUE=
 ### 1. X SRCDIR - specify the directory x is performed relatively to search the source code for these patterns. If there is no SRCDIR, the source will be searched relative to the module directory.
 ### 2. PACKAGE_PREFIX x - use if source paths relative to the SRCDIR does not coincide with the full class names. For example, if all sources of module are in the same package, you can create a directory package/name , and just put the source code in the SRCDIR and specify PACKAGE_PREFIX package.name.
 ###
-### @example:
+### @example: 
 ###  - example/ya.make
 ###
 ###        JAVA_PROGRAM()
@@ -6398,7 +6398,7 @@ macro _PY3_COMPILE_BYTECODE(SrcX, Src, Dst) {
 ### @usage: ARCHIVE_ASM(NAME archive_name files...)
 ###
 ### Similar to the macro ARCHIVE, but:
-### 1. works faster and it is better to use for large files.
+### 1. works faster and it is better to use for large files. 
 ### 2. Different syntax (see examples in codesearch or users/pg/tests/archive_test)
 macro ARCHIVE_ASM(NAME="", DONTCOMPRESS?"-p":"", REQUIREMENTS[], Files...) {
     .CMD=$ARCH_TOOL -q $DONTCOMPRESS ${input;join=\: :Files}: -o ${output;chksum;suf=$OBJ_SUF.rodata:NAME} ${requirements;hide:REQUIREMENTS} ${kv;hide:"p AR"} ${kv;hide:"pc light-cyan"}
@@ -6618,7 +6618,7 @@ macro NO_COMPILER_WARNINGS() {
 
 ### @usage: WERROR()
 ### Consider warnings as errors in the current module.
-### In the bright future will be removed, since WERROR is the default.
+### In the bright future will be removed, since WERROR is the default. 
 ### Priorities: NO_COMPILER_WARNINGS > NO_WERROR > WERROR_MODE > WERROR.
 macro WERROR() {
     ENABLE(WERROR)
@@ -6635,8 +6635,8 @@ macro NO_WERROR() {
 ### Disable C++ shadowing warnings.
 macro NO_WSHADOW() {
     ENABLE(NO_WSHADOW)
-}
-
+} 
+ 
 # tag:internal
 ### @usage: NO_PLATFORM_RESOURCES() # internal
 ### Exclude dependency on platform resources libraries.
@@ -6813,7 +6813,7 @@ macro GENERATE_ENUM_SERIALIZATION(File) {
     .CMD=$ENUM_PARSER_TOOL ${input:File} --include-path ${input;rootrel:File} --output ${output;chksum;suf=_serialized.cpp:File} ${output_include;hide:File} ${output_include;hide:"util/generic/serialized_enum.h"} ${kv;hide:"p EN"} ${kv;hide:"pc yellow"}
     .SEM=generate_enum_serilization ${input:File} ${output;hide;suf=_serialized.o:File} INCLUDE_HEADERS ${input;rootrel:File} ${tool;hide:"tools/enum_parser/enum_parser/bin"}
     PEERDIR(tools/enum_parser/enum_serialization_runtime)
-}
+} 
 
 ### @usage: GENERATE_ENUM_SERIALIZATION_WITH_HEADER(File.h)
 ###
@@ -6941,17 +6941,17 @@ SCHEEME2_STRUCT_INFO_FLAGS=-f "const static ui32 RecordSig" -u "RecordSig" --gcc
 ###
 ### Generates a C++ description for structure(contains the field RecordSig) in the specified file (and connected).
 ###
-### 1. ${scheeme_name}.inc - the name of the generated file.
+### 1. ${scheeme_name}.inc - the name of the generated file. 
 ### 2. Use an environment variable - DATAWORK_SCHEEME_EXPORT_FLAGS that allows to specify flags to tools/structparser
 ###
-### @example:
+### @example: 
 ###
 ###     SET(DATAWORK_SCHEEME_EXPORT_FLAGS --final_only -m "::")
 ###
 ### all options are passed to structparser (in this example --final_only - do not export heirs with public base that contains the required field,,- m "::" only from the root namespace)
-### sets in extra option
+### sets in extra option 
 ###
-### @example:
+### @example: 
 ###
 ###     SET(EXTRACT_STRUCT_INFO_FLAGS -f \"const static ui32 RecordSig\"
 ###         -u \"RecordSig\" -n${scheeme_name}SchemeInfo ----gcc44_no_typename no_complex_overloaded_func_export
@@ -7266,7 +7266,7 @@ TOUCH_JAVA_UNIT=$YMAKE_PYTHON ${input:"build/scripts/touch.py"} ${kv;hide:"java
 NO_CHECK_IMPORTS_FOR_VALUE=None
 ### @usage: NO_CHECK_IMPORTS([patterns])
 ###
-### Do not run checks on imports of Python modules.
+### Do not run checks on imports of Python modules. 
 ### Optional parameter mask patterns describes the names of the modules that do not need to check.
 macro NO_CHECK_IMPORTS(Masks...) {
     SET(NO_CHECK_IMPORTS_FOR_VALUE $Masks)