Feature Request - Additional logging for git command on makefile

[computeronix]

Could you consider adding additional logging for the git command when running on makefile / build?

Two scenairos:
-- add -v to git for just a tad but more info (regardless of DEBUG=0)
--When DEBUG=0 set GIT_TRACE=0 -> nothing changes
--When DEBUG=1 set GIT_TRACE=1 -> with this GIT_TRACE will provide deeper tracing for tracking

Put GIT_TRACE=x in with git command

The -v (verbose) and trace options in Git provide different levels of detailed output and are used for different purposes. Here’s a breakdown of the differences between them:

-v (Verbose)

• Purpose: Provides additional details and feedback about the command being executed.
• Use Case: Useful for getting more information about what's happening during a Git operation, such as cloning, pushing, pulling, or committing.
• Example:

  git clone -v https://github.com/opnsense/src.git /usr/src

trace

• Purpose: Provides very detailed debugging output, including internal Git operations and lower-level details about what Git is doing.
• Use Case: Useful for deep debugging and understanding the exact steps Git is taking, especially when troubleshooting complex issues.
• Environment Variables: To enable tracing, you set environment variables such as GIT_TRACE, GIT_TRACE_PACKET, GIT_TRACE_PERFORMANCE, etc.
• Example:

  GIT_TRACE=1 git clone https://github.com/opnsense/src.git /usr/src

Key Differences

• Level of Detail: trace provides much more detailed and low-level information compared to -v.
• Intended Audience: -v is useful for general users who need a bit more context, while trace is more suitable for developers or advanced users who need to debug and understand Git's internal processes.

Both options can be extremely helpful, but the trace option gives a more in-depth look under the hood, which can be invaluable for diagnosing tough issues.

Thank you again!

[fichtner]

As explained here #456 there's no point in tracing client communication that is caused by ancillary networking issues.

[fichtner]

We added #468 to make clone a little lighter, but we don't want to debug what git does during fetch over the network in our tools as it is irrelevant for the scope of the tools's purpose.