Subject: Re: [PATCH v3 5/7] builtin: patch-id: add --include-whitespace as a command mode

From: Junio C Hamano <[email-masked]>
Date: Fri, 14 Oct 2022 14:24:15 -0700

"Jerry Zhang via GitGitGadget" <[email-masked]> writes:

> +--include-whitespace::
> +	Use the "stable" algorithm described below and also don't strip whitespace
> +	from lines when calculating the patch-id.
> +
> +	This is the default if patchid.includeWhitespace is true and implies
> +	patchid.stable.

This seems very much orthogonal to "--stable/--unstable.  

Because the "--stable" variant is more expensive than "--unstable",
I am not sure why such an implication is a good thing to have.  Why
can we not have

    --include-whitespace --stable
    --include-whitespace --unstable

both combinations valid?