Emily Shaffer <emilyshaffer@xxxxxxxxxx> writes:
> ... To mark a config as safe,
> add "annotate:bugreport[include]" to the corresponding line in the
> config documentation; to mark it as unsafe, add
> "annotate:bugreport[exclude]" instead.
Hmph,...
> -sendemail.smtpEncryption::
> +sendemail.smtpEncryption annotate:bugreport[include] ::
> See linkgit:git-send-email[1] for description. Note that this
> setting is not subject to the 'identity' mechanism.
>
> @@ -15,7 +15,7 @@ sendemail.smtpsslcertpath::
> Path to ca-certificates (either a directory or a single file).
> Set it to an empty string to disable certificate verification.
>
> -sendemail.<identity>.*::
> +sendemail.<identity>.* annotate:bugreport[exclude] ::
So "sendemail.git-devel.cc" is not included due to [exclude] here,
but ...
> +sendemail.annotate annotate:bugreport[include] ::
> +sendemail.bcc annotate:bugreport[include] ::
> +sendemail.cc annotate:bugreport[include] ::
... "sendemail.cc" that is a fallback value for other "sendemail.*.cc"
is included?
> +++ b/generate-bugreport-config-safelist.sh
> @@ -0,0 +1,18 @@
> +#!/bin/sh
> +
> +cat <<"EOF"
> +/* Automatically generated by bugreport-generate-config-safelist.sh */
> +
> +
> +static const char *bugreport_config_safelist[] = {
> +EOF
> +
> +# cat all regular files in Documentation/config
> +find Documentation/config -type f -exec cat {} \; |
> +# print the command name which matches the annotate-bugreport macro
> +sed -n 's/^\([^ ]*\) *annotate:bugreport\[include\].* ::$/ "\1",/p' |
> + sort
We just care about "include" entries, so it does not matter whether
we mark entries with [exclude] or not anyway?
Puzzled...
