Emily Shaffer <emilyshaffer@xxxxxxxxxx> writes: > To be clear, do you want me to include the output of get_compiler_info() > in "git version --build-options" when I do that change, too? In the endgame, there are two kinds of information we'd want to gather and report, I would think. Ones that can be different per-binary are things like: - what version of the source code the binary was compiled from - with what compiler options - using which compiler and - linking with what libraries, - where in the filesystem is the binary located The others are various properties of the system the user is using, and having trouble using, Git on: - how many CPUs do we have, - how much free memory, - is the repository's filesystem case sensitive, - what version of 'wish' is being used. We'd want the former to be reported for each binary that matters, so "git version --build-options" would want to say it, "git remote-curl --build-options" would want to say it, and being different binaries, they may say different things. There is not much point in duplicating the latter that are not binary specific, so it probably makes sense to gather them inside, and report them from, "git bugreport" itself. Thanks.
