These are auto-generated files and should be ignored by git. Signed-off-by: Peter Tyser <[email protected]> --- This doesn't seem like the most sustainable long term solution. Every time we add a new auto-generated Config.in or Kbuild file we'll need to update a .gitignore file.
These .gitignore files could also be generated at runtime when the Config.in and Kbuild files are generated. However it would then be hard to determine if they should be removed during a 'make mrproper'. Anyone have any clever ideas? Or is maintaining .gitignore files worth the hassle? Thanks, Peter findutils/.gitignore | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) create mode 100644 findutils/.gitignore diff --git a/findutils/.gitignore b/findutils/.gitignore new file mode 100644 index 0000000..7a30caf --- /dev/null +++ b/findutils/.gitignore @@ -0,0 +1,3 @@ +# Config.in and Kbuild are auto-generated +Config.in +Kbuild -- 1.6.2.1 _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
