going

Functions that helps you can help someone else. If they don't break anything they are welcome and gets accepted into the code. Speed of acceptance further depends on review complexity.

Thank you all.
All fixed.

I apologize if I seem rude.
I use automatic translation.
Sometimes the meaning can turn over.
 
And thank you.
I started working with github.
Now I understand why you don't accept the patches as a patch file

Thanks. I saw the applied patches for testing.
I read your links and realized that it is customary to make changes in a separate branch and then pull request. 
Of course, first we need to discuss with the community the need to develop new functionality. I will do so in the future.
I'm currently laying out a number of patches that I think are the most important. Although it is not a tradition.
You can apply them on your own behalf, after testing, if you see them reasonable. I don't claim authorship.
Thank you for your understanding.

Thanks. It turned out two topics on one big question:
How to do better?
I will prepare an explanatory note and patch, or as you said:
I think then the two topics can be combined.

For me, these three points are a big problem.
If the founding fathers and users feel similar, I can provide a patch that fixes these issues.

I wish you all good health.
Using the "Armbian" build system, I noticed two bad points:
1 - incomplete cleaning of the source code before starting a new compilation, seen when patches add new files to the tree.
2 - Debian kernel source package includes the git directory.
 
1) All I do I'm fixing the version kernel (KERNELBRANCH="tag:v4.14.40") and collect several variants for one Board, changing the patchset for each version, adding or removing some.
Before each new compilation I'm doing a test of the purity of the source.
clean_repo() { display_alert "clean_repo $PWD" #git status -s git reset --hard HEAD # First, return the modified files. git clean -df # Then delete all new, added files. #git status } compile_kernel() { # A simple check ensures that we start with a clean slate. cd $SRC/cache/sources/$LINUXSOURCEDIR if [ "X$(git status -s)" != "X" ]; then clean_repo fi # ... ... }  
2) Manufacturer's code Debian package:      (--exclude='./.git/')
if [[ $BUILD_KSRC != no ]]; then display_alert "Compressing sources for the linux-source package" tar cp --directory="$kerneldir" --exclude='./.git/' --owner=root . \ | pv -p -b -r -s $(du -sb "$kerneldir" --exclude=='./.git/' | cut -f1) \ | pixz -4 > $sources_pkg_dir/usr/src/linux-source-${version}-${LINUXFAMILY}.tar.xz cp COPYING $sources_pkg_dir/usr/share/doc/linux-source-${version}-${LINUXFAMILY}/LICENSE fi can be changed to view:    (--exclude="[.]git")
if [[ $BUILD_KSRC != no ]]; then display_alert "Compressing sources for the linux-source package" tar cp --directory="$kerneldir" --exclude="[.]git" --exclude="[.]git[a-z]*" --owner=root . \ | pv -p -b -r -s $(du -sb "$kerneldir" --exclude="[.]git" --exclude="[.]git[a-z]*" | cut -f1) \ | pixz -4 > $sources_pkg_dir/usr/src/linux-source-${version}-${LINUXFAMILY}.tar.xz cp COPYING $sources_pkg_dir/usr/share/doc/linux-source-${version}-${LINUXFAMILY}/LICENSE fi